Closed Bug 1368585 Opened 9 years ago Closed 9 years ago

URL @ theatlantic.com causes Firefox to hang, needs a "force quit" to kill and restart.

Categories

(Firefox :: Untriaged, defect)

Product:
Firefox
Component:
Untriaged
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: ian.graham, Unassigned)

Details

Accessing this link: https://www.theatlantic.com/science/archive/2017/05/aliens-on-your-packard-bell/527445/ Causes Firefox to hang. Activity monitor says Firefox (not responding), and FF is pinned at ~100% cpu. System: OS X 10.11.6 Firefox: 53.0.3 (64-bit)
Summary: theatlantic.com → URL @ theatlantic.com causes Firefox to hang, needs a "force quit" to kill and restart.
Hello Ian, I couldn't reproduce this issue with user agent Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:53.0) Gecko/20100101 Firefox/53.0 CPU usage goes max to 8%. Try reproducing this issue in safe mode and with fresh profile. If Firefox hangs please get a crash report using the instructions at https://developer.mozilla.org/en-US/docs/Mozilla/How_to_report_a_hung_Firefox if you can and link the crash id here. Thanks!
Flags: needinfo?(ian.graham)
Status: NEW → UNCONFIRMED
Ever confirmed: false
Yes the page loads fine in safe mode. But if I only disable the extensions / add-ons, FF hangs (CPU 100%+; Activity monitor reports firefox as not responding) I am using only the default theme / default plugins, and do not use add-on services. Is there another set of instructions i can follow to try and diagnose further?
Flags: needinfo?(ian.graham)
It seems that we will have to drill down further using stack trace. It would be really helpful if you could force a crash using the instructions at https://developer.mozilla.org/en-US/docs/Mozilla/How_to_report_a_hung_Firefox and link the crash id here. It would be very helpful if you could also get Gecko Profile and attach it here. Instructions for capturing Gecko profile can be found here https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Reporting_a_Performance_Problem
Flags: needinfo?(ian.graham)
I am no longer able to reproduce this (made several attempts) so am marking RESOLVED -> WORKSFORME. Best guess as to why it works now: a) Fixed in June 13 FF (54.0) release b) fixed by a FF parameters reset after a FF force quit / restart.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(ian.graham)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.