[Konsole-devel] [Bug 184964] Konsole crash taking down ALL Konsole instances
robertknight at gmail.com
Wed Jun 10 21:15:42 UTC 2009
--- Comment #20 from Robert Knight <robertknight gmail com> 2009-06-10 23:15:21 ---
> Process per tab" is apparently "the thing" for web
> browsers at the moment. I think this would benefit Konsole also
As I described above, there is a big difference between what a web browser has
to cope with and what Konsole deals with.
1. For each tab, a web browser has to effectively run a complete application,
with a UI declaratively specified using HTML/CSS and with logic provided by a
perform network requests and so on. When you have all this interactive stuff
to keep track of, it makes sense to use the kernel to schedule these
applications and deliver good responsiveness and isolation. A terminal in
contrast, receives output, performs some simple 'drawing' operations on a
'canvas' and then renders that to the screen. When it receives input, it does
some simple translation of it and sends that to the terminal via a pipe.
The actual application itself containing the complex and fallible logic (the
already running in another process.
2. A web browser may have to embed Java, Flash, Silverlight etc. These are
all very large and complex pieces of code in themselves - all of them include a
complete JIT compiler for a start. A terminal's only inputs come from the file
system, the pty and the user.
Chrome/IE8/Safari's multi-process model makes sense because of the inherent
complexity of a web browser where the effort to do all the IPC is justified.
If you're finding the terminal unstable then I suggest the right cure would be
some good unit tests and refactoring of the problematic parts.
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