https://bugs.kde.org/show_bug.cgi?id=374009
--- Comment #22 from Niels van Mourik <ni...@nielsvm.org> --- Over the last 4 months, I have only had 4 occurrences of this issue. Since this is a drastic reduction compared to before that, for a long while I thought it was completely gone. It isn't, but the situation improved. I'm on Tumbleweed so releases roll quickly, current versions: qt: 5.11.1 kf5: 5.49.0 kwin: 5.13.5 (X11, OpenGL 2.0 now <-- so this changed) plasmashell 5.13.5 spectacle: 18.08.1 > I don't think Spectacle ... be hitting a code path in Qt, X, or > the graphics driver which some systems are unhappy with. (Note that in > Spectacle only the fullscreen rectangular selection tool is written in QML, > which makes use of OpenGL acceleration.) I agree on this, and I'm 100% sure that the rectangular selection tool is triggering or causing this issue. When it happens, I sometimes can't even draw the rectangle anymore, on other occasions I'm drawing the rectangle and the system breaks down. To be clear, drawing rectangles now works much more often than that that it breaks. > It's a bit hard to debug this without being able to reproduce, but at least > we can try to narrow down the nature of the problem. Could you record a > video of the hang and the events leading to it? As in the comments above > "hanging" is associated with multiple different issues, what are you doing > exactly in your case? Also, having a look at the memory and CPU usage of > all processes on the system during the hang would be great, maybe on a > console or via ssh?. This one is really hard to catch now that it happens so rarely and randomly. I did notice on one occasion though, that I could recover through Alt+SysRq+f which triggers the kernels OOM killer, suggesting this is memory related. My system has 8G of RAM and no swap partition enabled. > Any chance you could start Spectacle through "gdb" and interrupt it with > Ctrl-C while the hang occurs? Would GDB's remote debugging help, assuming > the network stack is still working? It happens really fast usually, half a second could be enough to have the entire system frozen beyond repair. It definitely feels that this freeze is GPU-related, since its similar to other issues I had in the past. Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) mesa: 18.1.7 kernel module: i915 This makes screenrecording and gdb close to impossible I think. Is it possible to somehow modify Spectacle's .desktop file to have it always go through GDB and log to disk everytime I use it? So that I could identify a faulty backtrace after reboot or Alt+SysRq+f? > One more thing to check is that you are indeed running only a single > Spectacle process (see Bug 386629 I just added some comments to). I can't rule this out, I sometimes make a lot of screenshots and forget that another Spectacle instance is left behind somewhere. The "cannot exit" issue 386629 also feels related. More evidence needed... -- You are receiving this mail because: You are watching all bug changes.
