Closed Bug 1171948 Opened 9 years ago Closed 9 years ago

Hang on http://dailycaller.com/section/entertainment/

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Version:
39 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox39+ disabled, firefox40+ wontfix, firefox41+ wontfix)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox39 + disabled
firefox40 + wontfix
firefox41 + wontfix

People

(Reporter: VarCat, Assigned: bugzilla)

References

Details

Environment:
FF 39.0b3
OS: Win 7 x64, Ubuntu 14.04 x86

STR:

1. Go to http://dailycaller.com/section/entertainment/
2. Scroll up and down through the page for like 10-15 sec

Issue:
The browser becomes unresponsive and after some time of unresponsiveness the following error is displayed:

"A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue.

Script: http://cdn01.dailycaller.com/w…des/js/wp-emoji-release.min.js:2"

Note:
1. Pressing to stop the script doesn't solve the issue.
2. This issue is not reproducible with dom.ipc.plugins.asyncInit set to false
3. This issues is reproducible on FF 40 DevEdition
Blocks: asyncplugininit
tracking-firefox40: --- → ?
tracking-firefox41: --- → ?
Flags: needinfo?(aklotz)
[Tracking Requested - why for this release]:
39 is also affected.
status-firefox39: --- → affected
status-firefox40: --- → affected
status-firefox41: --- → affected
tracking-firefox39: --- → ?
This is the NPN_Evaluate hang.
Flags: needinfo?(aklotz)
Wontfix for 39; I think since we're turning off async plugin init for 39 maybe this won't be an issue for 39 anyway.
status-firefox39: affected → wontfix
Assigning to Ben because all tracked bugs should have an assignee. Feel free to re-assign to whoever necessary.
Assignee: nobody → benjamin
I'll take it.
Assignee: benjamin → aklotz
Now this one is harder to repro; I think that changes to the embedded Flash content (ie, different ads) is the reason why. I'm working with the other bug that is duped with this one and seeing some results, though.
Aaron - What's the status of this bug? Did you have success in the other bug? (bug #?) Is this now resolved or a dup?
Flags: needinfo?(aklotz)
This bug is not reproducible on build:

FF 40 
Build Id: 20150730171029
OS: Win 7 x64, Mac Os X 10.10, Ubuntu 12.04 x86
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
I think we can consider these to be resolved/worksforme.
Flags: needinfo?(aklotz)
Setting wontfix since this bug is currently resolved/worksforme.
status-firefox40: affected → wontfix
status-firefox41: affected → wontfix
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.