Closed Bug 1101244 Opened 10 years ago Closed 10 years ago

[e10s] Tab crashed 'Try Again' button doesn't always work

Categories

(Firefox :: Tabbed Browser, defect)

36 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 963358
Tracking Status
e10s ? ---

People

(Reporter: raysatiro, Assigned: billm)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20141118030201

Steps to reproduce:

When a tab crashes there is a 'Try again' button. Sometimes that button doesn't work. I just started using these e10s nightlies and I'm crashing occasionally (see my other bug reports for context if you want) and often randomly. I'd say about 1/3rd of the time the try again button does nothing. Clicking the reload button always works regardless.

An easy way to reproduce this is bug #1101238 that will cause all tabs to crash.

Afterwards about half the tabs the try again button does nothing.


Actual results:

.


Expected results:

That depends but at the very least 'Try again' should load the tab I am in when I click on it.

Also, frankly when all tabs crash I think it would be good for there to be an option to reload all tabs. I understand from some other report that people want the ability to reload a single tab and I think that's useful, but if Firefox is aware all tabs have crashed there should be an additional button to reload all tabs.
tracking-e10s: --- → ?
Also, there is a similar open bug #963358 however that is for tabs with flash content. All my plugins are set to ask to activate except OpenH264. I typically have not enabled plugins on any page including many of those where the 'Try again' button doesn't work.
Another note, I said I'm crashing occasionally but that is not correct. What is correct is Nightly freezes occasionally and I have to terminate it.
Assignee: nobody → wmccloskey
Blocks: e10s
Component: Untriaged → Tabbed Browser
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.