Closed Bug 1261575 Opened 9 years ago Closed 9 years ago

[e10s] Pinned tabs should be reloaded eagerly after content process crash

Categories

(Core :: IPC, defect, P1)

Product:
Core
Component:
IPC
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1256280
Tracking Flags:
Tracking Status
e10s + ---
firefox48 --- affected

People

(Reporter: djc, Unassigned)

Details

(Keywords: ux-consistency)

After an e10s tab crash, despite the title being "This tab has crashed" (bug 1261574), it appears that actually all tabs are gone with it. This seems to have the effect of resetting the favicons on all tabs, but, even though Firefox eagerly loads pinned tabs for me normally on restart or after a main process crash, it does not do so after a tab crash.
We don't do this because the crash may have been caused by a pinned tab, which could trigger another crash.
Blocks: e10s-multi
That sounds sane. Maybe pinned vs not-pinned would be a useful division strategy for multiple content processes?
tracking-e10s: --- → +
Priority: -- → P1
bug 1256280 is a dupe of this, which is also a P1.
Let's dupe this to bug 1256280 because there's more info there. (FWIW, I would love for this to happen :)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.