View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0015065 | MMW v4 | Properties/Auto-Tools | public | 2018-08-30 13:09 | 2019-03-13 20:17 |
| Reporter | peke | Assigned To | |||
| Priority | immediate | Severity | crash | Reproducibility | unable to reproduce |
| Status | closed | Resolution | fixed | ||
| Target Version | 4.1.22 | Fixed in Version | 4.1.22 | ||
| Summary | 0015065: Auto-Organize: Crash MMW on the end of Auto-Organize (or saving properties sheet) | ||||
| Description | When user execute Auto Organize and MMW finish moving file, updating DB and should back to MMW it crashes. All operation is done and data is safe but only way to resolve problem user is to Reset all MMW settings, but preserving Library. I asked user to attach ELF log and problematic 1MediaMonkey.ini (renamed for backup). NOTE: Simple delete of Interface registry didn't fixed it, I wonder if I needed to delete rest like Status bar. P.S. As it is fixed for user he can't replicate anymore. | ||||
| Additional Information | DBZ-338-35348 KHM-209-22057 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1878 | ||||
|
|
Based on the crash log (attached in the ticket) it crashed after calling TWinControl.SetBounds in subsequent user32.dll|CreateWindowEx , so it could be an issue with incorrect window positions in the registry? Maybe on another monitor or multi-monitor environment? Hard to guess (as user has already deleted the registry). I tried to simulate to set negative values for positions X,Y but I don't see any crash. Assigned to Petr for review. In case of no idea we can just resolve as 'unable to replicate' and get the registry values next time (once there is another user with the same issue). |
|
|
Another instance of this crash callstack is BugReport__20180914080323.zip Ticket KHM-209-22057 , but for this user the crash appears after saving the Properties window. It also crashes after calling TWinControl.SetBounds in subsequent user32.dll|CreateWindowEx User is saying that the issue does not appear in 4.1.19.1859 |
|
|
Fixed |
|
|
Verified 1878 |
