https://bugs.kde.org/show_bug.cgi?id=431951
--- Comment #30 from griffiths_a...@icloud.com --- Agreed, the fundamental problem remains that it's having trouble for whatever reason waiting to lock a mutex before doing some operation and this locks up the whole UI. Logging the SQL was a roundabout way of trying to establish what its doing at that point. I don't have issues with any other application at the same time, there's plenty of memory, so no swap issues, no IO waits. I did a test with QT_LOGGING_RULES="qt.*=true", and there were still plenty of Qt messages when it locked up while still moving the mouse around, *BUT* they appeared to be: qt.qpa.events.reader: [heap] 202 qt.qpa.events.reader: [heap] 203 qt.qpa.events.reader: [heap] 204 qt.qpa.events.reader: [heap] 205 qt.qpa.events.reader: [heap] 206 qt.qpa.events.reader: [heap] 207 qt.qpa.events.reader: [heap] 208 qt.qpa.events.reader: [heap] 209 qt.qpa.events.reader: [heap] 210 etc.. which feels like the events were getting queued up. Could my issue be more Qt related? I appreciate that you can't replicate this issue so I just need a bit of guidance so I can provide you with enough info to sort this out. I don't have any other hardware / OS combination on which to test so I have to work with what I've got. -- You are receiving this mail because: You are watching all bug changes.
