mixxx unresponsive after finishing track

Bug #1900320 reported by Foss-4
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mixxx
Fix Released
High
Jan Holthuis

Bug Description

macOS 10.15.7
mixxx 7559

Process Sample (1 month): https://bin.disroot.org/?95d24f6e52e6a65b#6uzkpDw3dJd82ptNNa3Xa2kZ8yhgBTvhzqW7A6KGrMsa
Spin Dump (1 month): https://bin.disroot.org/?ccf5e051ba36885a#HeTBWNg1JCVtq8e1rtVsM8kPeXQVa4hscgB7LXACs7zc

mixxx CPU usage goes to 100% after playing a track.

This is always reproducible and started with one of the more recent master builds from the past 7 days or so.

Revision history for this message
Jan Holthuis (holthuis-jan) wrote :
Changed in mixxx:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Jan Holthuis (holthuis-jan)
milestone: none → 2.3.0
Revision history for this message
Foss-4 (foss-4) wrote :

Does this mean master builds are stuck again? Tested the most recent build.

Revision history for this message
Marco (c-moon) wrote :

I was also running into this issue. Short before the track has ended, the waveform got stuck (but sound was still OK), the CPU went to 100% and Mixxx was unresponsive.
I can confirm that this issue is already fixed in 2.3 branch (tested with commit 10e707ace5dc31fe53cf7e720fc908d8303ca5bf).

Revision history for this message
Foss-4 (foss-4) wrote :

Confirming the fix in 2.4.0-alpha-pre (build master r7564). Thanks Jan!

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/10171

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.