4 ms·
You mean one main "firefox" process that holds all tabs and one child process that holds all plugins (Flash, Acrobat). So if one tab hangs (e.g. WebGL demo) th
by frik 12y ago
You mean one main "firefox" process that holds all tabs and one child process that holds all plugins (Flash, Acrobat).
So if one tab hangs (e.g. WebGL demo) then still the whole Firefox is slow as hell. Firefox should finally spawn child processes for every other tab with less permissions ("sandbox" technique) so that if one tab hangs or crashes every other tab and the UI still is responsive. It seems we have to wait for Rust based Servo engine to get that feature - but that would also rescue us from XUL based UI (FirefoxOS already has an HTML5 based UI).
- ubercow13 12y agoIt's one process for tabs and one for the UI. Plugins have been in a separate process for years.
- dredmorbius 12y agoThat's still far less than optimal. Under Chrome (Chromium) I can kill individual tabs if they start getting sluggish. Not so w/ Firefox.
- dblohm7 12y ago"one child process that holds all plugins (Flash, Acrobat)." Not true. Each plugin module gets its own plugin container. Flash instances share a separate plugin-container from the one shared by Acrobat instances.
- the8472 12y agoyou can split the tabs over more than one process (by increasing dom.ipc.processCount), but that's even more experimental than e10s itself