Closed
Bug 1044349
Opened 11 years ago
Closed 11 years ago
Pipelight (silverlight) plugin hangs trunk build
Categories
(Core Graveyard :: Plug-ins, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: mar.kolya, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 (Beta/Release)
Build ID: 20140725060651
Steps to reproduce:
- On current ubuntu (14.04) install firefox-trunk (from ppa) and pipelight (from ppa)
- Open firefox-trunk and go to netflix account (subscription required, unfortunately).
- Start watching movie
Actual results:
After about 20s of watching movie you may notice that browser's UI stops responding - no buttons work.
After about 10-20s more video stops and browser hangs completely.
Expected results:
No UI locks, video hangs or browser hangs should happen.
FF 31 from Ubuntu doesn't have this problem, with same pipelight version.
Unfortunately current trunk version seems to break the only way to watch netflix.
| Reporter | ||
Comment 1•11 years ago
|
||
This is reproducible on clean profile as well, but you need some extension to substitute browser's UA string.
Updated•11 years ago
|
Component: Untriaged → Plug-ins
Product: Firefox → Core
Comment 2•11 years ago
|
||
Does this also happen with mozilla.org builds?
You need to collect a stack trace at the time of the hang. It would likely be useful to collect a stack from both the firefox process and the plugin-container process. Using stock mozilla.org builds you can follow these instructions: https://developer.mozilla.org/en-US/docs/How_to_Report_a_Hung_Firefox
But for Ubuntu builds you'll need to download the debuginfo packages and debug it locally.
Flags: needinfo?(mar.kolya)
| Reporter | ||
Comment 3•11 years ago
|
||
Looks like it doesn't happen any more on latest FF trunk and latest pipelight packages.
Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(mar.kolya)
Resolution: --- → WORKSFORME
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
•