mixxx unresponsive after finishing track

[Foss-4]

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.

[Jan Holthuis (holthuis-jan)]

Already fixed.

Related Zulip discussion: https://mixxx.zulipchat.com/#narrow/stream/109171-development/topic/100.25.20CPU.20after.20track.20ended
PR: https://github.com/mixxxdj/mixxx/pull/3176

[Foss-4 (foss-4)]

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

[Marco (c-moon)]

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).

[Foss-4 (foss-4)]

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

[Swiftb0y (swiftb0y)]

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