GUI freezes and unfreezes after a half minute again

[Jikstra]

Every now and than the mixxx gui freezes, gui is completely locked up but the sound is still playing. Also midi input is still working and modifying the sound output. Seems like only the gui freezes, all other parts are still working. The gui also unfreezes after a half minute or something, which is good, but still prevents me from using mixxx on a live environment.

Version: Tried latest version from arch & compiled latest master branch from git
OS: latest arch
CPU: Intel(R) Core(TM) i7-4800MQ CPU @ 2.70GHz
Logs: Will provide a log the next time this happens, or if anyone can tell me for what to look out i can provide logs. They are just many and big (never stopped session directly after this bug happend, will do next time)

[Jikstra (jikstra)]

Might be related to https://bugs.launchpad.net/mixxx/+bug/1789059

[Be (be.ing)]

Possibly, but with Bug #1789059, the GUI does not unfreeze, it stays frozen until Mixxx is forcibly stopped.

How many tracks do you have in your library? You may be encountering the well known but difficult to fix problem of all database transactions happening in the same thread as the GUI.

[Jikstra (jikstra)]

Oh you're right, also for him the controller doesn't work anymore, for me it does.

My library is "big"? I don't know, it has 3022 tracks. I play mostly from one crate which has ~2000 tracks in it.

[Be (be.ing)]

That's not a very big library. Ten times that would be a big library.

What waveform renderer are you using? Do you have a discrete GPU or are you using integrated Intel graphics? If you have a discrete GPU, what driver are you using?

Have you figured out how to reliably reproduce this?

[Jikstra (jikstra)]

> That's not a very big library. Ten times that would be a big library.

Good to know. No need to keep the library small ^^

> What waveform renderer are you using?

Waveform type is RGB (GLSL) and Waveform overwiew type RGB. Not sure if that's the waveform renderer, didn't see a different option which would fit your question better.

> Do you have a discrete GPU or are you using integrated Intel graphics? If you have a discrete GPU, what driver are you using?

I'm using the integrated intel graphics card.
$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
0

The driver package name is xf86-video-intel 1:2.99.917+831+ge7bfc906-1 and i think it's the default i915 kernel module.

> Have you figured out how to reliably reproduce this?

No, on my todays session it didn't happen (was around 50minutes). It just happens sometimes, next time i will immediatly stop mixxx and check/submit the logs.

[Be (be.ing)]

If you run mixxx with the "--logLevel debug" command line argument, you can watch the debugging output when it freezes.

[Jikstra (jikstra)]

> If you run mixxx with the "--logLevel debug" command line argument, you can watch the debugging output when it freezes.

Thanks for the info, yesterday evening it happend again (on the first track i played). I copied the mixxx.log, i hope it helps even with not specifiying the --logLevel debug thing.

It's attached to this comment.

[Jikstra (jikstra)]

Sorry, had to reupload the log.

[Be (be.ing)]

I don't see anything unusual in that log. I don't think we'll get useful information from the log unless you look at the output in a console when the bug happens so we can maybe have a hint what happens immediately before the bug.

[Be (be.ing)]

It might also help to watch the console output when the GUI unfreezes.

[Jikstra (jikstra)]

Okay, will use mixxx with --logLevel debug for the next times :)

[Jikstra (jikstra)]

It happend again yesterday but it wasa bit different. The main difference was that the gui only freezed for a couple seconds (less than 10 seconds). But I still want to share the console output, it seems more promising. --logLevel debug was set.

[Be (be.ing)]

Hmm, I don't see anything particularly alarming in that log. There are a handful of cache misses for CachingReaderWorker, but if there was any problem with that, I think it would affect the audio, not the GUI. Do you remember exactly at what line in the log it was at when the GUI stalled?

[Jikstra (jikstra)]

I don't know at which line this happend, but it happend on the last played track. Will further investigate it.

[RJ Skerry-Ryan (rryan)]

Just noting from the log that this is Qt 4.8.7. (Since it's in the 2.2.0 milestone I assumed Qt 5 was in use.)

[Be (be.ing)]

Oh, good catch. I assumed this was with Qt5 as well. Jikstra, please try compiling with Qt5, which is now the default. You can explicitly enable Qt5 by using the "qt5=1" option with scons.

[Jikstra (jikstra)]

Ooh good to know, will give it a try.

[Jikstra (jikstra)]

I tried the 2.3.0 develop version and the problem didn't occur, but others :D
Will give 2.2.0 with qt5 another try and see how this works.

[Be (be.ing)]

Jikstra, do you have any updates on this trying with Qt5?

[Be (be.ing)]

I am removing this from the 2.2.0 milestone unless it can be replicated with the current 2.2 branch using Qt5.

[Jikstra (jikstra)]

So i'm currently using the 2.2 branch compiled with qt5. I'm not getting this bug anymore, but still the gui freezes every now and then for a couple of seconds and then unfreezes again.

[Be (be.ing)]

A backtrace may be helpful. To run Mixxx in GDB, just run "gdb mixxx". Running in a debugger substantially slows down Mixxx, so I don't advise doing this while performing. Since there is no crash, you'll have to switch to the terminal and press Ctrl + C to interrupt Mixxx when this freeze occurs. Be warned that if a track is playing, you'll hear a harsh buzzing sound when you press Ctrl + C, so you may want to unplug or turn off your speakers. Once you've interrupted Mixxx, at the GDB prompt run "set height 0" then "thread apply all bt" and upload the backtrace here.

[Jikstra (jikstra)]

I guess this bug can be closed as it's not the initial problem anymore.

[Daniel Schürmann (daschuer)]

Do you have some hints what fixed the issue for you?

[Jikstra (jikstra)]

> Do you have some hints what fixed the issue for you?

It only happens with qt4. But that's a dead horse, only problem is i have other problems with qt5 :D But didn't open an issue yet because i lost myself while search through some bugs to find something similiar.

[Launchpad Janitor (janitor)]

[Expired for Mixxx because there has been no activity for 60 days.]

[Swiftb0y (swiftb0y)]

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