So, an app crashed, the crash handler window asking what to do with the crash pops up, and the system is very, very slow because of the crash.
Should I press Alt+F4 twice? Or the crash handler window understands I want to close the crashed app that triggered the crash handler?
The cursor gets to a very low frame rate and with very a lot of delay, so I can’t simply click on the option to close the crashed app.
If that’s not a thing, I will add this to the wishlist of the bugtracker.
Ex: Blender/video editor/A game crashes and slows down the system while you’re using your internet browser, so instead of super slowly trying to close it, all you needed to do was just press Alt+F4 on the crash handler window that pops up in front of whichever app you’re currently interacting with.
The message on the crash handler window should have “(Alt+F4)” added to the option that closes the the crashed app.
Edit: Moved to Brainstorm, since it makes more sense to be there now.
In my system which has only 6Gb of RAM the worst offenders of this are Firefox and Thunderbird. It had gotten so bad that I had to create a global custom shortcut “Ctrl+K” that I set to immediately kill all instances of Firefox and Thunderbird regardless of where the focus is. Mind you, when the system has stalled (to the point that FernandoMMuniz described) then even the shortcut might take 10-15 minutes to execute.
I really hope you find a solution to this, but I’m afraid that your scenario sounds very much like a low memory situation that your whole software stack (including the kernel) is failing to handle correctly, not only Plasma.
