https://bugs.kde.org/show_bug.cgi?id=372114
Jiri Palecek <jpale...@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jpale...@web.de --- Comment #25 from Jiri Palecek <jpale...@web.de> --- Hello the problem here seems to be the fact that KConfig instances are *totally* not thread safe, and the freeze protection thread uses the same one as the main thread. When they stomp over each other, this crash ensues. I'll attach a proposed patch to use a different KConfig instance. On a deeper note, is that freeze check really necessary, safe and effective? I would say 99%+ of times the freeze alarm goes off, it is actually the system thrashing after startup/closing a big application (like a game), when all of the other applications are resizing their windows/repainting and not really an opengl driver freeze (of these duplicates, only bugs 372078, 373485 seem to be genuinely related to the graphics. Any thoughts on that? -- You are receiving this mail because: You are watching all bug changes.