This sounds like a deadlock in the GUI thread. Hard to trace if there is no common pattern for triggering the issue. It might be caused by a signal loop of direct slot connections.
I've not seen this here on Fedora 28, yet. Disclaimer: I'm using the new multithreaded analysis code. That shouldn't make a difference if you don't re-analyze your tracks upon loading.
This sounds like a deadlock in the GUI thread. Hard to trace if there is no common pattern for triggering the issue. It might be caused by a signal loop of direct slot connections.
I've not seen this here on Fedora 28, yet. Disclaimer: I'm using the new multithreaded analysis code. That shouldn't make a difference if you don't re-analyze your tracks upon loading.