Closed Bug 1066653 Opened 10 years ago Closed 10 years ago

[e10s] Reviving tabs after the content process crashes doesn't work

Categories

(Firefox :: Tabbed Browser, defect)

Product:
Firefox
Component:
Tabbed Browser
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1065785
Tracking Flags:
Tracking Status
e10s m3+ ---

People

(Reporter: ttaubert, Unassigned)

References

Details

Using the STR from bug 1066647 I can make the content process crash. I assume that we have a single content process for now and this is why all tabs crash at once. When I click the button to revive a single (all?) tab(s) it seems to start loading but never finishes. Some tabs have the right labels, some switch to "New Tab".
This is probably the worst bug I've hit in testing - I lost a bunch of tabs this way (after a restart they are completely lost).
I hit this crash shortly after startup:
https://crash-stats.mozilla.com/report/index/dc9a14b8-54be-41c1-82ff-19ce02140915

which triggered the behaviour above.  I force-quit and edited prefs.js to reset browser.tabs.remote.autostart before starting back up, and didn't end up losing my tabs.  If you don't want to lose your tabs, try that.
It seems that crashing the content process is quite easy by loading a bunch of tabs at once. If that's exactly what we do when reviving all crashed tabs then... well it won't work :)
Depends on: 1068210
We can workaround this problem for M2 with bug 1065785. blassey thought we already had an M3 bug for this problem. I see related bugs, but no duplicate.
tracking-e10s: ? → m3+
This will get taken care of by bug 1065785. That's an M3, but at the top of my M3 priority list.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.