Closed
Bug 1176876
Opened 10 years ago
Closed 10 years ago
Deadlocking when loading one specific page
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mity, Unassigned)
References
()
Details
(Keywords: hang, in-triage, Whiteboard: [gfx-noted])
Attachments
(1 file)
|
408.23 KB,
application/x-zip
|
Details |
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150525141253
Steps to reproduce:
Tried to load http://www.bbc.com/travel/story/20150512-the-master-of-japans-ancient-tattoo-tradition
System: OS X 10.8.5
Firefox: 38.0.5
Actual results:
Deadlock. Firefox got completely unresponsive.
100% reproducibility (at least on my machine).
Expected results:
The page should be loaded normally, and if there is any error in it, it should report it or refuse to load it. It should not hang all application.
| Reporter | ||
Updated•10 years ago
|
OS: Unspecified → Mac OS X
Comment 1•10 years ago
|
||
Does this still happen if you disable flash ? It works for me...
Flags: needinfo?(mity)
| Reporter | ||
Comment 2•10 years ago
|
||
Happens even when I disable the Shockwave Flash plugin as well all the other plugins.
Also, it seems it is not really a dead-lock. The Firefox starts to eat 100% of CPU, making the application unresponsive, or almost unresponsive (clicking to close the tab and waiting a minute until it really closes revives it again).
Flags: needinfo?(mity)
Comment 3•10 years ago
|
||
Seeing as you can get it to not die completely, can you try to generate a profile using the builtin browser toolbox? Steps:
Open the web dev toolbox (cmd-opt-i)
go to the devtools settings pane
tick the "enable chrome and add-on debugging" and "enable remote debugging" checkboxes
Under Tools > Web Developer open the "Browser Toolbox"
accept the connection request dialog
go to the "profiler" tab
prepare the URL in a new tab (ideally, make sure no other tabs are open)
click the "start profiling" button in the browser toolbox
load the problematic URL
wait for the problematic behaviour to start
stop profiling
close the tab
You should then be able to save the profile and upload it as an attachment here (you may need to compress it).
Flags: needinfo?(mity)
| Reporter | ||
Comment 4•10 years ago
|
||
I could not find any tab named "Profiler". I created a profile on a tab called "Performance". Is that what you mean?
Flags: needinfo?(mity)
| Reporter | ||
Comment 5•10 years ago
|
||
Forgot to mention I closed the tab after just a few secs. I guess it is better for analyzes if it is not overly long. However I can retry for longer time duration if needed.
Comment 6•10 years ago
|
||
(In reply to Martin Mitáš from comment #4)
> Created attachment 8627259 [details]
> Performance profile (zipped)
>
> I could not find any tab named "Profiler". I created a profile on a tab
> called "Performance". Is that what you mean?
Yes, sorry, I wrote the steps largely from memory. I think the tab got renamed recently. Anyway, this sounds perfect, I will try to investigate more soon, but I'm digging myself out from a post-Whistler queue of stuff to be looking at, so it might be later this week (hopefully tonight/tomorrow).
Flags: needinfo?(gijskruitbosch+bugs)
Comment 7•10 years ago
|
||
I'm very sorry it took me such a long time to look at this. It looks like the majority of the time is spent in
"DecodePool::SyncDecodeIfPossible"
with a blob URI, which is apparently caused by "drawWatermark" in the BBC's script (main.js).
Seth, can you look into this?
Also, Martin, can you still reproduce this on later versions of Firefox (e.g. version 39, current release, or 40, current beta (https://beta.mozilla.org/ ), or nightly: https://nightly.mozilla.org/ ) ?
Component: Untriaged → ImageLib
Flags: needinfo?(gijskruitbosch+bugs) → needinfo?(seth)
Product: Firefox → Core
| Reporter | ||
Comment 8•10 years ago
|
||
Tried 39 and nightly (42.0a1.en-US.mac).
Reproduced in both of them.
Updated•10 years ago
|
Whiteboard: [gfx-noted]
Comment 9•10 years ago
|
||
Did the site change? I don't see high cpu on the url.
| Reporter | ||
Comment 10•10 years ago
|
||
@Thimothy: As far as I can tell, the site is still the same but I cannot reproduce anymore with Firefox 43.0.4 so it is likely fixed.
Comment 11•10 years ago
|
||
(In reply to Martin Mitáš from comment #10)
> @Thimothy: As far as I can tell, the site is still the same but I cannot
> reproduce anymore with Firefox 43.0.4 so it is likely fixed.
Thanks for the quick response! Let's mark this wfm - we can always reopen if this reoccurs or we figure out we've missed something.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(seth)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•