https://bugs.kde.org/show_bug.cgi?id=492506
--- Comment #11 from Oded Arbel <o...@geek.co.il> --- Interesting repro. I don't see `drm_commit_thread.cpp` in my stack traces, though it may be related. I see that the `drm_commit_thread.cpp` is not in the main thread - next time I get a freeze I will try to identify the thread that is busy looping - though from the flame graph I believe it is the harfbuzz renderer on the main thread. While all of the repros on my device are with external screens dominik.klementow...@protonmail.com connected to a laptop, I don't believe connecting/disconnecting has anything to do with that it - and specifically on another device I got a freeze with just an internal laptop screen that was never connected to an external screen. All in all, I think my report is a different issue than dominik.klementow...@protonmail.com 's - but if that ever get fixed I'm OK with closing this issue - until I can repro it again 😏. -- You are receiving this mail because: You are watching all bug changes.
