interface crawls/hangs when all songs highlighted during BPM/waveform analysis

Bug #1084751 reported by RAWRR
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
Medium
Unassigned

Bug Description

Using 1.11.0-beta2-pre (build r3503), 1.73ghz dual core, 2.99gb ram, onboard Realtek spu w/ASIO4ALL.

Anyway, you know how in the Analyze pane, you click the "select all" button, all the songs get highlighted, you click analyze, and thats how you run analysis on your complete collection? I do that and it starts the process running on all of my songs, but the interface is so laggy as to be virtually unresponsive until I click a song so that only one song is highlighted. Then the interface is reasonably responsive (considering the task it is running). If I leave all of them highlighted, it obviously is choking unbelievably, the mouse won't even move across the interface without delaying and jumping. The files I was analyzing numbered around 4300.

This happened twice so far, the first time I killed Mixxx figuring something had gone wrong. When I tried it again, it happened again and I realized then that it only happened when I left all the songs highlighted.

Since all of the tracks remain highlighted by default after a complete library analysis has begun, this is a problem. A simple fix would be to automatically unhighlight all songs after the process begins, but this seems odd enough that maybe something else is wrong with the stuff.

Thanks for looking into it guys!

Changed in mixxx:
status: New → Confirmed
assignee: nobody → Daniel Schürmann (daschuer)
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Any progress?

Changed in mixxx:
importance: Undecided → Medium
RAWRR (rawrr)
tags: added: library polish
removed: freeze hang lag laggy
Revision history for this message
Daniel Schürmann (daschuer) wrote :

No, I will free this now.

Changed in mixxx:
assignee: Daniel Schürmann (daschuer) → nobody
Revision history for this message
RAWRR (rawrr) wrote :

I think this may be fixed now anyway. I 'm running this on a pretty resource-constrained machine with 3,626 tracks highlighted and it doesn't seem to be laggy at all.

tags: added: analyzer
removed: analysis analyze bpm polish
Revision history for this message
Uwe Klotz (uklotzde-deactivatedaccount) wrote :

Should be fixed in 2.1 with changes on how tracks are cached.

Will finally fixed in 2.3 with the multi-threaded analysis that doesn't block the UI when selecting and analyzing a large number of tracks.

Changed in mixxx:
milestone: none → 2.3.0
assignee: nobody → Uwe Klotz (uklotzde)
status: Confirmed → Fix Committed
Changed in mixxx:
status: Fix Committed → Fix Released
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6727

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.