| |||||||||||||
Solid release...Solid release...Posted Jan 26, 2012 9:59 UTC (Thu) by moltonel (guest, #45207)In reply to: Solid release... by renox Parent article: KDE 4.8 released
It's easy enough to build a more bug-resilient and debuggable desktop by having widgets in separate processes... But (most ?) desktops have moved away from that to use less memory, less runtime overhead, and be easyer to develop.
(Log in to post comments)
Solid release... Posted Jan 26, 2012 12:18 UTC (Thu) by renox (subscriber, #23785) [Link]
If memory serves, you can configure Chrome from having everything in the same process to each tab in a different process (the default is somewhere in between), I wonder if it wouldn't be possible to do the same for a desktop?
Maybe this could help debugging?
Solid release... Posted Jan 26, 2012 18:33 UTC (Thu) by nix (subscriber, #2304) [Link]
The default is 'each tab rendered by a different process, WebGL and plugins in their own processes, each domain gets its own process too'. You can optionally combine some or all of the processes into one (turning them into threads instead), but I don't think you can make it more processy than it already is.
|
|||||||||||||