View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0021331 | MMW 5 | General | public | 2024-11-06 22:56 | 2024-11-14 19:24 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 5.1 | ||||
| Target Version | 5.1 | Fixed in Version | 5.1 | ||
| Summary | 0021331: Background tasks (Volume analysis) block UI process performance (regression 5.1) | ||||
| Description | Whenever Volume Analysis is occurring CPU usage is relatively low, BUT when other operations are initiated (e.g. playback, mass-edit, auto-tag) UI interactions/refreshes become very slow. This doesn't occur with 5.0.5 | ||||
| Steps To Reproduce | 0 Verify that performance CPU core settings are set to their defaults (1 core/process) / priority for background tasks: lower 1 Navigate to Ratings > Unknown [List] (with Artwork and Track Volume columns displayed). It can be any large list with 1000+ tracks 2 Select 200 tracks with missing Track volume and initiate volume analysis 3 Initiate playback 4 Scroll through the list --> Notice how Artwork displays very slowly (much slower than 5.0.5)! 5 Select tracks from an album and initiate auto-tag --> The operation proceeds _very_ slowly (much slower than 5.0.5)! 6 After the lookup completes, press the 'Tag & Continue' button --> MM takes about 5s to respond! | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3073 | ||||
|
|
In doing more tests of auto-tag, I observed (and recorded videos/logs) several issues: 1) Slow performance of auto-tagging in MMW 2024 compared to MMW5. This is illustrated in Autotag-performance-issues_and_crash-on-cancel 2) The auto-tag UI's 'Tag and continue' button responds very slowly (as described in the original report) when clicked. Illustrated in: - Volume-analysis_lows_UI - UI-faster_without_volume-analysis 3) On another occasion, if I initiated auto-tag while Analyze volume was running in the background, and then pressed Cancel in the auto-tag dialog --> crashlog 20E33B10 4) If I cancelled auto-tag without volume analysis running in the background it resulted in --> crashlog AD2A..... This occurs at the end of the video/debug log: Autotag_performance_issues_and_crash-on-cancel It's unclear to me whether these all have the same root cause or not. My suspicion is that there are 3 related issues: A) volume analysis somehow interferes with other processes (UI and ?perhaps Indy?) B) Once Indy is broken, auto-tag lookups perform poorly even when MMW is restarted (IIRC we had previously dealt with Indy failures persisting across MMW restarts in MMW4) EDIT: I'm not sure what causes auto-tag lookups to become super slow i the manner described above. Originally I'd thought that it was Indy-related, but on further testing, the bug occurs even after restarting the machine (i.e. Auto-tag is always failing now even though it worked previously with this build). So I'm no longer sure what the cause is. C) Auto-tag cancellation is brittle and though it normally works, the connectivity issues caused by B) result in cancellation crashing I'll share the logs/videos directly to the MM5 group. |
|
|
I have problem with reproduction of the performance problem, for me it is not so different, but I have most probably found the cause, please test. Fixed in build 3073. |
|
|
Verified 3073. Leaving 'resolved' for Peke to fully test leveling functionality. |
|
|
Verified 3074 Even I have not been able to make any significant difference, but I can confirm no crashes and even see 1-3% less CPU use on 3074 against 3070 |
