View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017446 | MMW 5 | Tagging / organizing (properties / auto-tools) | public | 2021-01-27 16:25 | 2021-02-11 01:17 |
| Reporter | Ludek | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0 | ||||
| Target Version | 5.0 | Fixed in Version | 5.0 | ||
| Summary | 0017446: Closing MM5 while tagging tracks can result in crash | ||||
| Description | 1) Select 10000 tracks, right click > Properties > Cutsom 2) change a custom tag or custom field and click [OK] => 10000 tracks are updating in a thread with progress on the bottom 3) close MM5 => MM5 closed without a prompt This leaves many of tracks not updated or updated only partially (to database and not file tag) and potentially can result in crash while tagging (LL sent me one) MM5 should prompt (like MM4): "'There are background processes running. Terminate them?'" and then gracefully close in case of user termination | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2302 | ||||
|
|
Fixed in 2300 New string added to translate: 'There are background processes running. Terminate them?' (already translated in MM4) |
|
|
Verified 2301 Prompt shows correct in 2301 |
|
|
Updated this string for all completed languages. |
|
|
Last night I experienced an issue closing MM5 2301. On close, it would show 'There are background processes running. Terminate them?' even though no background processes were showing in MM. I haven't replicated it, and was only started running dbgview once the issue was occurring. Does that log provide enough info? |
|
|
No, the log does not show the task (very probably the task ended just right before showing the dialog) There must have been a bacrground task with progress before initiating the dialog, might it be the "Lyrics searching..." task ? |
|
|
It occurred again this morning and I have a full log this time. The only thing I did was: 1 Initiate playback 2 Minimize to microplayer 3 Restore 4 Stop playback 5 Close There were no 'hourglasses' or status indicators in MM that a background process was running, but each attempt to Close MM results in the error. |
|
|
|
|
|
Fixed in 2302 + implemented self closing of the dialog once all tasks are finished |
|
|
Verified 2308 Unable to crash using initial steps and steps from 0017446:0061636 |
