View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017966 | MMW 5 | General | public | 2021-06-01 02:35 | 2021-06-18 20:30 |
Reporter | rusty | Assigned To | |||
Priority | urgent | Severity | crash | Reproducibility | random |
Status | closed | Resolution | fixed | ||
Product Version | 5.0.1 | ||||
Target Version | 5.0.1 | Fixed in Version | 5.0.1 | ||
Summary | 0017966: Invalid pointer operation | ||||
Description | This issue occurred randomly after I'd started MM 5.0.1.2410 following a force-close necessitated by a focus problem with the artwork dialog (clicking Artwork in the Preview Window opened the Artwork in full size, but focus was lost and MM became non-responsive). Hopefully the debug log is of use. | ||||
Tags | No tags attached. | ||||
Attached Files | |||||
Fixed in build | 2412 | ||||
|
Based on the debug log it was "Invalid pointer operation" in the thread that was starting media server, but that's all that I see. Do you have crash log (EL)? Then I could see also the thread callstack, but not seeing any crashlog submitted here from you -- the last one is from build 2408 on 05/27/2021 |
|
BTW: The log looks very similar to LowLander's log from 0017928 : the "Invalid pointer operation" is after the line "Disabling antifreeze detection" -- so it looks rather something related to the Eureka's "Disabling antifreeze detection" -- to find more... |
|
OK, "Disabling antifreeze detection" is called right before the Eureka (crash log) window pop-ups -- so that it is not subsequently detected as "freeze exception" . So having crash log (EL) would be valuable here to see more. |
|
Note that there was no crash log generated. |
|
This just occurred again on 2411 as follows: 0 Set laptop to extend primary screen to a monitor (WIN-P > Extend). Settings are: 'Size of text, apps, and other items:' 150%, Primary: 1920x1080, Secondary: 3440 x 1440 1 Run MM in secondary monitor 2 Start dragging the window to the first monitor --> Invalid pointer operation Debug log and crashlog attached (note: there was no crashlog notification) |
|
This looks exactly like 0017928 and is "Invalid pointer operation" on MM start, based on the "invalid-pointer_build-2411.LOG" it was in the thread [6400] while loading plugins (after f_wave.dll load) 'Invalid-pointer_build-2411_MediaMonkey.el' is of any use as it is log from the browser process (MediaMonkey.exe) and not from the render process (MediaMonkeyEngine.exe) that crashed. Assigned to Michal as he replicated this issue once and seems to be related to plugin loading ? This would also explain why Eureka did not catch it -- as C++ plugins are not compiled with Eureka |
|
Based on last logs from Michal and Rusty it is a problem when writing INI settings |
|
Fixed in 2412 |
|
Verified 2412 I and user observing the issue could not replicate anymore. Close after second confirmation. |
|
Closing after testing with 2417 Also no new user reports are filed and I could not replicate it anymore. |