EXCEPTION_ACCESS_VIOLATION_READ on Firefox 50
I really need some help right here. Mozilla Firefox keeps crashing for no reason. I either get "Bad news first: This tab has crashed" or Mozilla Crash reporter opens up. This started happening to me lately.
I've tried everything, from running a System Scan (which found no corrupted files) to using a different profile, and nothing helped. This is a new hard drive that was installed just three or four days ago. Please help me.
Here are my last five crash reports:
bp-289f9e59-bcf7-4096-a84e-e4d082161119 2016-11-18 7:12 PM bp-209c33fe-f4cb-40ab-9bbc-624402161119 2016-11-18 7:02 PM bp-39ad67b8-a542-451f-82a9-9baeb2161119 2016-11-18 6:53 PM bp-018e5728-87da-48ae-9bde-836b52161119 2016-11-18 6:45 PM bp-f0313ab3-8db1-4c0c-9c1a-7ddcc2161118 2016-11-18 12:51 PM
All of which happened today.
Усі відповіді (7)
bp-289f9e59-bcf7-4096-a84e-e4d082161119
Signature: nsPurpleBuffer::VisitEntries<T>
KERNELBASE.dll = Microsoft
ntdll.dll = Microsoft
This is for Sumo's Related Bugs 1318810 UNCONFIRMED --- Crash in nsPurpleBuffer::VisitEntries<T> ++++++++++++++++++++++++++++++++++++++++++++++++ bp-209c33fe-f4cb-40ab-9bbc-624402161119
Signature: nsPurpleBuffer::VisitEntries<T>
combase.dll = Microsoft
user32.dll = Windows User API
KERNELBASE.dll = Microsoft
ntdll.dll = Microsoft
This is for Sumo's Related Bugs 1318810 UNCONFIRMED --- Crash in nsPurpleBuffer::VisitEntries<T> +++++++++++++++++++++++++++++++++++++++++++ bp-39ad67b8-a542-451f-82a9-9baeb2161119
Signature: js::ConstraintTypeSet::sweep
KERNELBASE.dll = Microsoft
ntdll.dll = Microsoft
This is for Sumo's Related Bugs 1287306 NEW --- SIGSEGV @ js::ConstraintTypeSet::sweep when archiving a message in Thunderbird 1220385 NEW --- crash in js::ConstraintTypeSet::sweep 1174997 NEW --- Crash in js::ConstraintTypeSet::sweep ++++++++++++++++++++++++++++++++++++++++++++++++++ bp-018e5728-87da-48ae-9bde-836b52161119
Signature: js::DispatchTyped<T>
KERNELBASE.dll = Microsoft
ntdll.dll = Microsoft
This is for Sumo's Related Bugs 1266870 RESOLVED DUPLICATE crash in js::AtomizeString and other signatures, starting 2016-04-21
1260754 RESOLVED DUPLICATE crash in js::DispatchTyped<T>
Perform a System File Check to fix corrupted system files Win 7, 8, 10, Vista: https://support.microsoft.com/en-us/kb/929833 Win XP: https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/system_file_checker.mspx?mfr=true
FredMcD said
Perform a System File Check to fix corrupted system files Win 7, 8, 10, Vista: https://support.microsoft.com/en-us/kb/929833 Win XP: https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/system_file_checker.mspx?mfr=true
Hello Fred. I have tried doing that. No corrupt files were found. Still crashing.
I called for more help.
FredMcD said
I called for more help.
Hello Fred. I have tried refreshing Firefox, and it's still crashing.
The "Bad news first" tab crash message appears when Firefox is running with a new multiprocess feature. Here's some more information on that:
e10s
One of the headline changes in Firefox 48+ is e10s, which separates the browser interface process from the page content process. The performance impact of this can vary a lot between systems: many users find it faster, some find it slower, for many it's neutral. Hopefully by the time all the kinks are worked out it will work smoothly for everyone.
Are you using e10s?
You can check whether you have this feature turned on as follows. Either:
- "3-bar" menu button > "?" button > Troubleshooting Information
- (menu bar) Help > Troubleshooting Information
- type or paste about:support in the address bar and press Enter
In the first table on the page, check the row for "Multiprocess Windows" and see whether the number on the left side of the fraction is greater than zero. If so, you are using e10s.
If you are using e10s:
To help evaluate whether that feature is causing the crashes, you could turn it off as follows:
(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.
(2) In the search box above the list, type or paste autos and pause while the list is filtered
(3) Double-click the browser.tabs.remote.autostart.2 preference to switch the value from true to false
Note: the exact name of the preference may vary, but it will start with browser.tabs.remote.autostart
At your next Firefox startup, it should run in the traditional way. Any difference?
Oh, maybe you already tried that because it was suggested toward the end of one of your other threads: https://support.mozilla.org/questions/1146910
Could you update us on that?