[Konsole-devel] [Bug 184964] Konsole crash taking down ALL Konsole instances

Matthew Woehlke mw_triad at users.sourceforge.net
Wed Jun 10 21:36:21 UTC 2009


--- Comment #21 from Matthew Woehlke <mw_triad users sourceforge net>  2009-06-10 23:36:15 ---
> As I described above, there is a big difference between what a web browser has
> to cope with and what Konsole deals with.

Occasionally, Konsole crashes. Or maybe I even do something insane like 'kill
<some konsole pid>' by accident. Or maybe the pty goes haywire and does
something that breaks Konsole's internal state (or just makes it
non-responsive, in which case a 'close tab' button that knows 'the window with
<pid> is not responding' is easier to deal with than finding the pty pid,
assuming that killing the pty would even be sufficient for Konsole to recover).
I would MUCH rather either the container crash-and-burn (and be restartable
with no pty loss at all), or a single tab die. Besides that isolating the
history (memory space) is no bad thing...

If you don't want to do any proactive work (i.e. not worry about this until NWI
becomes reality), that's one thing, but your objection sounds like "well my
code is so perfect that it never crashes, so I have no reason to minimize the
disastrousness of a crash". Need I say more?

While "don't crash" is obviously a good goal, I think a Konsole crash (as
things stand now) is painful enough that "crash without taking out 20+ pty's"
isn't an unreasonable idea. If a crash only took out a singly pty, I'd be more
inclined to agree, but right now that's not the case.

Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the konsole-devel mailing list