Comment 16 for bug 1789059

Revision history for this message
Marc Ranolfi (marc.2377) wrote :

I've been getting this on Mixxx 2.2.4 (which somehow was released to Arch Linux much sooner than the official release which was just yesterday) for the past 5 days or so. Maybe the fact that I'm running JACK with tighter settings and two external USB soundcards, and streaming with OBS studio at the same time (loading my CPUs to ~35%) makes the problem more apparent.

It seems to happen somewhat randomly when loading tracks at times of high cpu load. I got it on video - was streaming live, in fact (unlisted, thankfully): https://www.youtube.com/watch?v=RnhlpDaXFB8&t=17m14s. See at the 17:24 mark. The music continues to play fine (I have JACK running at RTPRIO 85 (PR -86), which means the mixxx client thread is PR -81. There's another thread at priority -2 and the remaining threads are not real-time (PR 20).

I get this on the stock Arch kernel, as well as linux-ck and linux-rt (with/without CONFIG_HZ=1000 and other optimizations), which is to say, it happens with all kernels and config sets.

The log file does not contain anything useful and running with --developer also did not help. Attached backtrace according to comments #4 and #15.

As I've been able to reproduce this consistently (with a bit of patience), do let me know if I can be of any more help.