https://bugs.kde.org/show_bug.cgi?id=513666
--- Comment #7 from Roke Julian Lockhart Beedell <[email protected]> --- (In reply to Nate Graham from comment #6) > It's really nobody's fault; it's a necessary outcome of exceeding a limit. > > If you don't want to experience problems from exceeding the limit, increase > the limit, or don't do the thing that makes you encounter the limit. My worry is that on lower-power, mobile devices, I'd (as a layman) presume that the ANR threshold is lower. Therefore, reaching this limit becomes easier, especially when one doesn't close applications in the background (as is normal for mobile users), and, therefore, doesn't close old shells. In that context, having the shell become unresponsive isn't ideal, for there's no TTY to switch to without a keyboard. I want to transition to postmarketOS where possible on my low-end mobile devices, so I want to mitigate these paper-cuts. The fact that I had a cat sitting on my keyboard first reproduce this is mere coincidence. It's not like the other issue about the terminal exiting on high tab counts, where the solution, albeit very crude, is simply to not reach a specific limit; this problem progressively increases as more shells exist. -- You are receiving this mail because: You are watching all bug changes.
