Firefox crashes on specific yet random pages.
This started happened recently. I haven't installed anything new such as plugins or add-ons; All I've done is update my windows and laptop drivers but I doubt that has anything to do with the situation.
When opening certain pages, Firefox just suddenly closes and a "Plugin-Container.exe has stopped working" window opens 4-5 times. Websites include:
- Youtube.com - Not the homepage, but the video page. Also note that playing embedded videos doesn't crash, but they don't play. - The Mozilla Support Question Creation page - The page I used to make this question kept crashing. Opening it in with add-ons disabled works. [This page :https://support.mozilla.org/en-US/questions/new/desktop/fix-problems/form?search=Firefox+crashes&step=aaq-question] - This random page: http://blog.oscarliang.net/choose-lipo-battery-charger-power-supply/ - The troubleshooting information page [about:support]. Opening it in with add-ons disabled works.
The pages don't seem to have anything in common. What I've tried to do:
- Scan my PC for malware. - Reset my Firefox to default settings in 'Troubleshooting Information'. - Update Shockwave and FlashPlayer.
Crash report: https://crash-stats.mozilla.com/report/index/f82ec83e-aedc-43b0-8821-93c262150806
Any help would be appreciated.
Penyelesaian terpilih
Title of that Bug report. Crash in atiumdag.dll with old AMD drivers
Update your video / graphics drivers and see what happens. If that type of crash continues disable Hardware Acceleration in Firefox. https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration
Baca jawapan ini dalam konteks 👍 0All Replies (2)
Penyelesaian Terpilih
Title of that Bug report. Crash in atiumdag.dll with old AMD drivers
Update your video / graphics drivers and see what happens. If that type of crash continues disable Hardware Acceleration in Firefox. https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration
Rolling back and re-installing the update seems to have fixed this. Thanks for your swift answer :D