Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Firefox Constantly Crashing on Specific Website - What Gives?

  • 2 réponses
  • 2 ont ce problème
  • 1 vue
  • Dernière réponse par cor-el

more options

Firefox 56/Windows 10 crashing FREQUENTLY on www.washingtonpost.com, when attempting to access "comments" section. As is true with many sites, there are many handoffs and links flashing at the bottom before the "Comments" page fully loads. If one scrolls during this process, FF crashes. The page will restore quickly via the "Restore All Tabs" button in the Crash Report box, but chances are it will crash again two or perhaps three times before becoming stable. Rarely (today being an example), the page will crash FF without ANY user interaction, i.e., no scrolling. I've experienced this on only ONE other website; I visit perhaps a dozen each day reading news. FF stable on 95% of what I view.

I've alerted the www.washingtonpost.com e-staff to this problem, but have not heard anything from them. The fact that it happened once on a different site leads me to believe its not a specific unique problem to the Washington Post, but there is something about that site that exploits a weakness if FF and causes crashes.

Of course, every time it crashes, a crash report is sent to Mozillo. Perfectly willing to share other data... Just tell me how to get it to you. Oh -- I've completely reloaded FF once, and am currently running Windows anti-virus protection, plus recently scanned with Avast and Malwarebytes --- everything OK.

Firefox 56/Windows 10 crashing FREQUENTLY on www.washingtonpost.com, when attempting to access "comments" section. As is true with many sites, there are many handoffs and links flashing at the bottom before the "Comments" page fully loads. If one scrolls during this process, FF crashes. The page will restore quickly via the "Restore All Tabs" button in the Crash Report box, but chances are it will crash again two or perhaps three times before becoming stable. Rarely (today being an example), the page will crash FF without ANY user interaction, i.e., no scrolling. I've experienced this on only ONE other website; I visit perhaps a dozen each day reading news. FF stable on 95% of what I view. I've alerted the www.washingtonpost.com e-staff to this problem, but have not heard anything from them. The fact that it happened once on a different site leads me to believe its not a specific unique problem to the Washington Post, but there is something about that site that exploits a weakness if FF and causes crashes. Of course, every time it crashes, a crash report is sent to Mozillo. Perfectly willing to share other data... Just tell me how to get it to you. Oh -- I've completely reloaded FF once, and am currently running Windows anti-virus protection, plus recently scanned with Avast and Malwarebytes --- everything OK.

Toutes les réponses (2)

more options

Same problem for me on WSJ, WaPo and Bloomberg. I think It's javascript related. Amazon also had this problem with Firefox for a while. Nobody home there at Mozilla. Sad...

more options

If you have submitted crash reports then please post the IDs of one or more recent crash reports that start with "bp-".

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You can find the report ID of recent crash reports "on the "Help -> Troubleshooting Information" (about:support) page".

  • click the "All Crash Reports" button on this page to open the about:crashes page and see all crash reports.

Alternatively you can open about:crashes via the location/address bar.

See also: