Closed
Bug 1129236
Opened 9 years ago
Closed 9 years ago
[e10s] Plugin hang locks up browser
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: vladan, Unassigned)
Details
Attachments
(1 file)
5.88 KB,
text/plain
|
Details |
I got a minute-long hang after loading a globalnews.ca page containing Flash objects. Eventually a notification bar gave me the option of killing the plugin, which allowed the session to resume. I could not reproduce the bug on the same URL. See attached console log.
Reporter | ||
Comment 1•9 years ago
|
||
On second look, the console log mostly contains DevTools issues -- I did try to open the Error Console after I noticed the hang.
Aside from the plugin hanging, it sounds like everything worked as expected here. To debug the plugin hang, it would be useful to have stacks from the content process and the plugin process.
Reporter | ||
Comment 3•9 years ago
|
||
Is the Plugin Hang UI being ported to e10s? http://dblohm7.ca/blog/2012/11/22/plugin-hang-user-interface-for-firefox/
Summary: Plugin hang locks up e10s browser → [e10s] Plugin hang locks up browser
No. The notification bar replaces the hang UI. Was there anything about the hang UI that was superior to the notification bar? If so, please mention it in bug 1119442.
Reporter | ||
Comment 5•9 years ago
|
||
Yes, I think the hang UI did have some advantages, but I'll let the hang-UI author comment on bug 1119442
I'm going to close this for now since it's not reproducible. If you get the plugin hang again, please try to get stacks for the main, content, and plugin processes.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•