Closed Bug 1191910 Opened 9 years ago Closed 9 years ago

[e10s] Browser hangs with e10s enabled (2 out of 2 times)

Categories

(Core :: General, defect)

41 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
e10s ? ---
firefox41 --- affected

People

(Reporter: ritu, Unassigned)

References

Details

Attachments

(1 file)

This has happened 2 out of 2 times on Aurora41 with e10s enabled.

plugin-container.exe is spinning at 25% CPU usage on my win8 laptop.

STR with e10s enabled:
1. Open a bunch of tabs.
2. I have gmail on tab1, linkedin on tab2, facebook on tab3, macys.com tab4, jcpenney.com tab5, cnn.com tab6, huffingtonpost.com tab7
3. On huffingtonpost tab find a post with over 300 comments and click to see comments.
4. Go to task manager and kill flash process.
5. On huffingtonpost tab, notice a message about flash process has crashed.
6. leave browser running for a few hours.

Expected results: Browser should be responsive and work ok.

Actual results: Browser hangs and plugin-container.exe for Aurora is spinning at 25%CPU usage.
[Tracking Requested - why for this release]: Browser hangs are bad.
No need to track 41 since e10s won't be enabled there again.

Interesting steps to reproduce. Lets let this fall into normal e10s triage.
I ran into the crash again now. This time without doing any kill on Flash plugin process.

STR this time:
1. A regular session on window1 with 8 tabs.
2. Open a new window, open care.com tab1, cnn.com tab2, gmail.com tab3
3. Go back to window1

Notice hang.
(In reply to Ritu Kothari (:ritu) from comment #3)
> I ran into the crash again now. This time without doing any kill on Flash
> plugin process.
> 
> STR this time:
> 1. A regular session on window1 with 8 tabs.
> 2. Open a new window, open care.com tab1, cnn.com tab2, gmail.com tab3
> 3. Go back to window1
> 
> Notice hang.

Do you have addons enabled? If so try reproducing with addons disabled to see.

Also, are you generating and crash reports from this? If chrome is hung and you wait for around 45 seconds you should get a crash dialog.
Which OS(s) do you see this on?
As mentioned in comment 0, I am using windows8.
Rita,  Devs would like to see your about:support. Would you attach a copy of it here, please? Thanks.
Flags: needinfo?(rkothari)
Tracy, sorry it took me a long time to respond to this one, but please see the txt file attached which is a copy of my Aurora42 about:support.
Flags: needinfo?(twalker)
Ritu,  Thank you for posting that info.  Since you have three add-ons enabled, please try to reproduce the bug after disabling them all. If, you're unable to reproduce with all your add-ons disabled. Re-enable them one by one to test against which may be causing the trouble.
Flags: needinfo?(twalker)
Flags: needinfo?(rkothari)
See Also: → 1197077
Ritu - can you reproduced this in release?

I suspect it is one of the two hangs (which are very similar) from bug 1207766 or bug 1209235.
They seem to have been masked (at least partially, possibly fully) when Fx41 was in Beta.

It would be also be interesting if you can reproduce on Aurora Fx43, as we think they are now fixed by another change (bug 1185639 and bug 1189709, which have been requested to be uplifted to release).
Hi Bob, I tried to repro this bug but when I force kill plugin-container.exe for Dev Edition, all the tabs crashed. This was on 43.0a2 build ID: 20151007004048. Is this expected? I would say content crash like this is worse/almost as bad as the hang I used to notice weeks earlier.
Flags: needinfo?(rkothari) → needinfo?(bobowen.code)
(In reply to Ritu Kothari (:ritu) from comment #12)
> Hi Bob, I tried to repro this bug but when I force kill plugin-container.exe
> for Dev Edition, all the tabs crashed. This was on 43.0a2 build ID:
> 20151007004048. Is this expected? I would say content crash like this is
> worse/almost as bad as the hang I used to notice weeks earlier.

Are you sure you killed the NPAPI process?
If you killed the content process then it would be expected for all the tabs to show as crashed.
Flags: needinfo?(bobowen.code) → needinfo?(rkothari)
(In reply to Bob Owen (:bobowen) from comment #13)
> (In reply to Ritu Kothari (:ritu) from comment #12)
> > Hi Bob, I tried to repro this bug but when I force kill plugin-container.exe
> > for Dev Edition, all the tabs crashed. This was on 43.0a2 build ID:
> > 20151007004048. Is this expected? I would say content crash like this is
> > worse/almost as bad as the hang I used to notice weeks earlier.
> 
> Are you sure you killed the NPAPI process?

Hi Bob, yes, I killed plugin-container.exe

> If you killed the content process then it would be expected for all the tabs
> to show as crashed.

It did not do that in the past. It would hang after a while which is why I reported this bug.
Flags: needinfo?(rkothari)
(In reply to Ritu Kothari (:ritu) from comment #14)
> (In reply to Bob Owen (:bobowen) from comment #13)
> > (In reply to Ritu Kothari (:ritu) from comment #12)

> > 
> > Are you sure you killed the NPAPI process?
> 
> Hi Bob, yes, I killed plugin-container.exe

Confusingly, plugin-container.exe is used for all our child processes, including the content process.

The command lines are different, the easiest way to spot it is at the end ... content process has "tab", NPAPI process has "plugin".
The command line seems to get truncated in Task Manager, but if you use Sysinternals Process Explorer you can either hover over the executable name and it displays the command line (or you can select it to be displayed separately, but then you loose it in the hover text).
(In reply to [:tracy] Tracy Walker - QA Mentor from comment #10)
> Ritu,  Thank you for posting that info.  Since you have three add-ons
> enabled, please try to reproduce the bug after disabling them all. If,
> you're unable to reproduce with all your add-ons disabled. Re-enable them
> one by one to test against which may be causing the trouble.

Ritu, can you reproduce without addons?
Flags: needinfo?(rkothari)
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(rkothari)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: