Tabs Crashing, Unable to Determine Cause
First I had problems with Facebook Messenger crashing a tab, attempting to fix that has resulted in Facebook in general just crashing a tab. Similarly had problems with Google Maps and the Adobe Flash website, with the browser completely crashing on certain sites.
For the most part things worked fine in Safe Mode, but the cause doesn't seem to be a plugin. I've also done a completely clean re-install of Firefox, but no joy.
Hardware acceleration is disabled.
Done everything I can find as solutions, but no luck.
Crash reports: bp-44ed7404-5ca6-428d-8bb7-7ad920190706
bp-1e22151c-e5bd-4611-a559-c79530190706
Giải pháp được chọn
Try to disable WebGL if you do not need it. Set this pref to false on the about:config page.
- webgl.disabled = true
- https://support.mozilla.org/en-US/kb/about-config-editor-firefox
You can try to disable hardware acceleration in Firefox.
- Options/Preferences -> General: Performance
remove checkmark: [ ] "Use recommended performance settings"
remove checkmark: [ ] "Use hardware acceleration when available" - https://support.mozilla.org/en-US/kb/performance-settings
Close and restart Firefox after modifying the setting for changes to take effect.
You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.
Đọc câu trả lời này trong ngữ cảnh 👍 0Tất cả các câu trả lời (5)
Ok, copy and pasted data from a profile on my main computer (problem is on a laptop that I am using).
Restored Facebook, but Messenger is still crashing. Chrome installed as backup and Facebook is fully functional on that, but Firefox is my preferred browser.
Please try the following
1. Open task manager and monitor RAM usage while browsing. To do this open task manager, go to Performance at the top then select Memory.
If RAM is pinned (near or at 100%) then Firefox is crashing due to a RAM limitation
Note: If it is caused by RAM you could uninstall programs you don't use as they might be using RAM in the background
2. Turn on hardware acceleration
Hope this helps!
Giải pháp được chọn
Try to disable WebGL if you do not need it. Set this pref to false on the about:config page.
- webgl.disabled = true
- https://support.mozilla.org/en-US/kb/about-config-editor-firefox
You can try to disable hardware acceleration in Firefox.
- Options/Preferences -> General: Performance
remove checkmark: [ ] "Use recommended performance settings"
remove checkmark: [ ] "Use hardware acceleration when available" - https://support.mozilla.org/en-US/kb/performance-settings
Close and restart Firefox after modifying the setting for changes to take effect.
You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.
Dannomac said
Please try the following 1. Open task manager and monitor RAM usage while browsing. To do this open task manager, go to Performance at the top then select Memory. If RAM is pinned (near or at 100%) then Firefox is crashing due to a RAM limitation Note: If it is caused by RAM you could uninstall programs you don't use as they might be using RAM in the background 2. Turn on hardware acceleration Hope this helps!
Negative on the RAM usage, 65% usage when the tab crashed.
stormwell55 said
First I had problems with Facebook Messenger crashing a tab, attempting to fix that has resulted in Facebook in general just crashing a tab. Similarly had problems with Google Maps and the Adobe Flash website, with the browser completely crashing on certain sites. For the most part things worked fine in Safe Mode, but the cause doesn't seem to be a plugin. I've also done a completely clean re-install of Firefox, but no joy. Hardware acceleration is disabled. Done everything I can find as solutions, but no luck. Crash reports: bp-44ed7404-5ca6-428d-8bb7-7ad920190706 bp-1e22151c-e5bd-4611-a559-c79530190706
Disabling WebGL appears to have fixed it, vaguely recall it was something that I had to do some months back. Recently Firefox had to do a clean install rather than update itself (cited it was too out of date), which would've led to WebGL being enabled and probably the cause of my problems.
Still, thank you.