Comment 10 for bug 1805559

I tried, but I don't know how to get any useful information from that. Running "frame Xlib-frame-number" then "info args" and "info local" didn't yield any useful information, I think because I didn't have the source code files for the library. If you have any tips how to get more useful info, please let me know. But at this point, I think the best course of action is to hack around the bug. Considering I have encountered at least two distinct situations (this bug and Bug #1789059) that trigger the same Xlib bug, I'm not confident that if we change Mixxx to not trigger the Xlib bug in this one case that we won't discover more code in Mixxx later that also triggers the Xlib bug.

I do use JACK and I haven't tested if this happens with ALSA, but nothing in the backtrace leads me to suspect this has anything to do with audio processing. The audio thread continues fine when the GUI thread deadlocks, which allows me to recover relatively gracefully by letting the track continue to play till the end, then force quitting and restarting Mixxx.