Firefox tab crashes repeatedly for particular website
Firefox tabs crash repeatedly for a particular email website that I am using. Specifically, the tab crashes when I click on an link to open an email and see the email contents. The tab will not crash every single time, just occasionally (i.e. sometimes I am able to read an email without the tab crashing, other times not). I do not think that the timing of the crashing has anything to do with the email contents (e.g. length, format). I also do not think that the tab crashing issue is happening for any other websites. The crashing started recently, sometime late December.
I installed the latest version of Firefox, and I cleared the web cache, but nothing has changed.
Any suggestions?
Gekozen oplossing
Thank you for your reply.
I've isolated the problem. I was able to use email normally while Firefox was in troubleshooting mode. Through process of elimination I was able to determine that the Firefox plugin NoScript 11.2.14 was the source of the problem. Which is strange because I've been using this plugin with this email program for many, many years without issue. (I might as well tell you the name of the email program, which is desknet's NEO V4.0 R1.2).
It appears that the NoScript version changed last year on December 30th, which corresponds with when the tab crashing started: https://addons.mozilla.org/ja/firefox/addon/noscript/versions/
Anyhow, thanks for your help. I think that we can safely say that the current issue is not a Firefox problem but a Firefox extension problem, specifially a NoScript problem.
Dit antwoord in context lezen 👍 0Alle antwoorden (8)
Please provide a public link (no password) that we can check out. No Personal Information Please !
In the address box, type about:crashes<enter>.
Note: If any reports do not have BP- in front of
the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 Submitted crash reports, and copy them. Now go to the reply box and paste them in.
Please, Do not post a screenshot ! !
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
Thank you for your reply.
Unfortunately, the email website in question is not accessible to the public. I tried accessing the website from a different much newer computer and there were no crashing problems that I could see. Also, for what it is worth, tabs were crashing so frequently yesterday the email website was unusable, but today I've had only experienced two crashed tabs.
Here is the most recent 10 submitted crash reports:
bp-26d01957-68ac-4c27-ba15-8b5120220106 2022/01/06 9:08 表示 bp-27c316fd-a40a-4a27-b6a4-6d0e30220106 2022/01/06 9:08 表示 bp-5da87836-d0c8-4989-861f-dc94f0220105 2022/01/06 8:41 表示 bp-b58f7c2c-74d8-420a-9216-71cf50220105 2022/01/06 8:41 表示 bp-1386b0ac-d56b-4634-bdc7-2cbcd0220105 2022/01/06 8:41 表示 bp-4475db30-22f3-466b-aea1-cef140220105 2022/01/06 8:41 表示 bp-29716192-7ad0-4252-89e8-895a20220105 2022/01/06 8:41 表示 bp-ce640ffb-236f-4674-8d9e-17a980220105 2022/01/06 8:41 表示 bp-e6582586-ff40-41d5-a115-4596f0220105 2022/01/06 8:41 表示 bp-854bd997-1b2e-4d33-b19a-7a19a0220105 2022/01/06 8:41 表示 bp-32c00268-c3c1-44af-ace6-0f1970220105 2022/01/06 8:41 表示
Product Firefox Release Channel release Version 95.0.2 Build ID 20211218203254 (2021-12-18) Buildhub data OS Windows 10 OS Version 10.0.19043
bp-26d01957-68ac-4c27-ba15-8b5120220106 bp-27c316fd-a40a-4a27-b6a4-6d0e30220106 bp-5da87836-d0c8-4989-861f-dc94f0220105 bp-b58f7c2c-74d8-420a-9216-71cf50220105 bp-1386b0ac-d56b-4634-bdc7-2cbcd0220105
Signature: nsContentList::ContentAppended
Crash Reason EXCEPTION_ACCESS_VIOLATION_READ
This is for Sumo's Related Bugs 292033 RESOLVED WONTFIX setting document.body.innerHTML hangs/crashes Gecko [@ nsContentList::ContentAppended]
Bug 292033 Opened 17 years ago Closed 14 years ago
I called for more help.
What were you doing at the time? surfing, watching a clip, reading something . . . .
Start Firefox using Troubleshoot(Safe) Mode {web link}
A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?
Thank you for your reply.
The tab crashes when I am checking email. A list of emails is displayed in the middle-above section of the website and email contents are displayed in the middle-below section inside a frame (i.e. clicking on an email from the list will cause the email contents to be displayed below). When I click on an email in the middle-above section the browser tab sometimes (but not always) crashes. I am not seeing any crashing tabs for any other websites currently.
What is your e-provider? Is that website the only place Firefox crashes?
Many site issues can be caused by corrupt cookies or cache.
Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.
- How to clear the Firefox cache {web link}
If there is still a problem,
Start Firefox using Troubleshoot(Safe) Mode {web link}
A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?
While you are in Troubleshoot(Safe) mode;
Try disabling graphics hardware acceleration in Firefox. Since this feature was added to Firefox it has gradually improved but there are still a few glitches.
How to disable Hardware Acceleration {web link}
Gekozen oplossing
Thank you for your reply.
I've isolated the problem. I was able to use email normally while Firefox was in troubleshooting mode. Through process of elimination I was able to determine that the Firefox plugin NoScript 11.2.14 was the source of the problem. Which is strange because I've been using this plugin with this email program for many, many years without issue. (I might as well tell you the name of the email program, which is desknet's NEO V4.0 R1.2).
It appears that the NoScript version changed last year on December 30th, which corresponds with when the tab crashing started: https://addons.mozilla.org/ja/firefox/addon/noscript/versions/
Anyhow, thanks for your help. I think that we can safely say that the current issue is not a Firefox problem but a Firefox extension problem, specifially a NoScript problem.
That was very good work. Well Done. You should contact NoScript support for more help if you need it.