Closed
Bug 1099863
Opened 10 years ago
Closed 10 years ago
Hang on flash initialization
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1095807
People
(Reporter: evilpies, Unassigned)
References
Details
Attachments
(2 files)
The flash plugin seems to hang during initialization, which sadly also makes the rest of the browser hang. Killing the plugin-container works. Happened to me on:
http://www.bbc.com/news/blogs-trending-30055278?ocid=socialflow_twitter
|
||
Comment 1•10 years ago
|
||
Looks like this is with e10s? Can you see whether the plugin process is at 0% or 100% CPU and capture a stack from it if it's stopped?
Flags: needinfo?(evilpies)
|
Reporter | |
Comment 2•10 years ago
|
||
Doesn't seem to be at 100%. I already posted the stack in my first comment. This might actually be caused by click-to-play, which I have activated for Flash.
Flags: needinfo?(evilpies)
|
|
||
Comment 3•10 years ago
|
||
Oh, I read that as a content-process stack. If this is with e10s, what are the stacks of the chrome and content process?
If this is non-e10s, I just need the chrome process.
Flags: needinfo?(evilpies)
|
||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
|
|
Reporter | |
Comment 5•10 years ago
|
||
Yes this is with e10s, I attached a stacktrace for all three involved processes.
Flags: needinfo?(evilpies)
|
||
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•