3 ms·
IIRC per-tab e10s already exists, just isn't enabled by default yet because it has some rough edges. The Rust part of your comment is irrelevant. There is Rust
by Manishearth 10y ago
IIRC per-tab e10s already exists, just isn't enabled by default yet because it has some rough edges.
The Rust part of your comment is irrelevant. There is Rust code shipping in Firefox, but nowhere near the amount needed for observable changes in behavior. Work is being done to put larger components in but nothing is shipping yet. Also, IME most crashes are asserts (in all browsers) and that's not a problem Rust fixes. If you get a segfault-based crash please report it, it could be exploitable. (report normal crashes too, really)
- Animats 10y agoIf process-per-tab is enabled, can each tab crash separately, or does the whole browser still have to go down?
- Manishearth 10y agoThey should crash separately. I'm not sure of the details.
- Manishearth 10y agoIt seems like the dom.ipc.processCount setting sets the total number of content processes to use. Note that this means that tabs will share content processes, so a crash in one tab may crash a few others. You can reduce this by ramping up the number of processes, though that can lead to bloat. No idea how stable this is right now. For me, on Dev Edition with regular multiprocess mode enabled, things work fine and I don't get crashes.