Firefox basically unusable on new PC but other browsers work fine??? (Linux and Windows)
Hey, so I've just spent the past weekend attempting to troubleshoot this issue and nothing is working.
The issue: Firefox either crashes (only Linux) or slows down drastically alongside a CPU temp spike (Linux and Windows). Temps are 25 Celsius at idle, 30-40 while using Firefox for the first few minutes, and then it spikes up to 55-65 Celsius and never drops back down to normal unless I close the browser. Chromium-based browsers like Chrome, Brave, Edge all run fine with no crashes, no slow down, and normal temps.
Things I've tried to troubleshoot the issue:
- Reinstalled Firefox
- Tried troubleshoot mode
- Updated drivers
- Enabled and disabled hardware acceleration
- Made some configurations (media.ffmpeg.vaapi.enabled set to true, accessibility.force_disabled set to 1)
- Tried both Wayland and Xorg on Linux, changed the window protocol to wayland instead of xwayland
- Changed operating systems (Fedora, Arch Linux, Windows 10)
- Reinstalled Fedora and Arch
- Disabled XMP profile in BIOS
- Performed Memtest (no errors)
And a few of my crash reports:
- https://crash-stats.mozilla.org/report/index/c4600e0b-80c5-4c1d-a4ca-783a40221212
- https://crash-stats.mozilla.org/report/index/81164758-f350-41d3-862e-db0e30221211
- https://crash-stats.mozilla.org/report/index/2e6fe761-c74b-4fb1-9862-1821b0221211
- https://crash-stats.mozilla.org/report/index/b0b385ad-8c71-4f5a-9a1c-8446b0221212
- https://crash-stats.mozilla.org/report/index/380c25a3-c109-4fc1-b1d8-17ba70221212
- https://crash-stats.mozilla.org/report/index/a19af1cf-656b-49a9-bc1a-7c4de0221212
- https://crash-stats.mozilla.org/report/index/a81cd713-9d75-4e9b-adb0-341cb0221212
- https://crash-stats.mozilla.org/report/index/ffe07939-cc6e-490a-be1b-6a3160221212
- https://crash-stats.mozilla.org/report/index/f68e8cb0-74a2-48d9-977c-908830221212
- https://crash-stats.mozilla.org/report/index/91f8f817-b6f8-47d7-a029-170800221212
Perhaps I'm spending too much time into this but I really want to know what is causing this and whether it's pertaining to my hardware or Firefox itself. Any help appreciated.
Izabrano rješenje
Fixed the issue by simply clearing the CMOS. Everything running perfect now.
Pročitaj ovaj odgovor u kontekstu 👍 2Svi odgovori (6)
If Firefox previously worked but suddenly doesn't start, it may be due to some corrupt data in your settings. Uninstalling and reinstalling Firefox would not fix this problem because your settings are not removed on uninstall. To test to see if this is the problem, use the Profile Manager to create a new profile.
Greetings,
Jimmy
Also try downloading Firefox from Mozilla, unzip, and run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
Operating System: openSUSE Tumbleweed 20221210 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.10-1-default (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Xeon® CPU E3-1535M v6 @ 3.10GHz Memory: 62.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics P630 Product Name: HP ZBook 17 G4
jonzn4SUSE said
Also try downloading Firefox from Mozilla, unzip, and run firefox-bin from the folder and see if you have the same issue. https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
I tried this and unfortunately ran into the same issues with the browser slowing down, CPU temps and fans spiking, and then crashing.
And this is what came up in the terminal:
[cal@cak firefox]$ ./firefox-bin ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:46:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:53:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:53:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:53:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T15:53:50Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:03:28Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:03:28Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:03:28Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:03:28Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:06:09Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:06:09Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:06:09Z ERROR mp4parse] Found 2 nul bytes in "\0\0" [2022-12-12T16:06:09Z ERROR mp4parse] Found 2 nul bytes in "\0\0" ExceptionHandler::GenerateDump cloned child 14996 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [cal@cak firefox]$ Failed to open curl lib from binary, use libcurl.so instead ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. [2022-12-12T16:38:07Z ERROR glean_core::metrics::ping] Invalid reason code startup for ping background-update
techguy150 said
If Firefox previously worked but suddenly doesn't start, it may be due to some corrupt data in your settings. Uninstalling and reinstalling Firefox would not fix this problem because your settings are not removed on uninstall. To test to see if this is the problem, use the Profile Manager to create a new profile. Greetings, Jimmy
Firefox hasn't previously worked on this PC but I still tried creating a new profile and encountered the same issues.
Odabrano rješenje
Fixed the issue by simply clearing the CMOS. Everything running perfect now.
Good work! ;-))