frequent crashes. on Linux

Hi, this looks really bad from the reports, it's basically crashing on random places. This is not caused by a single place hitting a limit somewhere, this just completely unstable, from the ground up.

If you restart into Troubleshoot Mode (from Help menu) to unload all addons, is there any change?

I'd recommend running a good hardware test, esp. with load tests of memory segments, to rule out any HW fault.

Is Zorin updated? "It seems to happen more often when I'm watching video" AMD driver https://help.zorin.com/docs/hardware/ CPU / GPU Temperature?

After I posted this, I don't fully remember what I did. There was one or two more crashes before I closed FF for the night. bp-91be494d-2e41-42b7-9330-e49630260913 13/09/2026, 11:16 bp-e0ac525c-a6c7-4af5-abe8-0ab5e0260913 13/09/2026, 11:16

I'd spent a lot of time beforehand mucking about in the logs and program files trying to pin down what made things crash. I'd managed to stop a startup program that I'd thought I'd deleted and was tripping lots of errors. I removed and re-downloaded Firefox twice. I think without system files the 2nd time? For a while I was checking graphics drivers and that was a dead end. Maybe-related, the Updater seems to be very confused that I removed Brave browser from my system (came with the distro). Anyway, I have no hope of exactly reproducing what happened. I do know how to pull up logs for the machine (separately from the crash logs on Firefox).

I went to sleep, and I woke up this morning and things were okay? I did have one freeze/crash mid-day but I didn't even have FF open so it's likely unrelated...? got these back: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed A start job for unit UNIT has finished with a failure. The job identifier is 472 and the job result is failed. bgscan simple: Failed to enable signal strength monitoring gkr-pam: unable to locate daemon control file GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed

Otherwise, I've been able to use FF normally today. It's... strange.

If you guys think the issue is my hardware, and not FF itself, then I guess I'll take my question to the next relevant place... checking hardware. But I don't actually know how to do that. I've been using Linux a year, I can use Terminal, but I'm not exactly a whiz and I'm not sure what software is safe to use to check the hardware status.

lol and I got a crash right now. smh bp-26431cfb-22ed-479e-adc3-3e3380260913 13/09/2026, 22:37

computer logs say, Privileged Cont: Exiting due to channel error. firefox-bin: ExceptionHandler::GenerateDump minidump generation WRRende~ckend#0 : ExceptionHandler::WaitForContinueSignal waiting for continue signal... ExceptionHandler::SendContinueSignalToChild sent continue signal to child

and etc

in short: is the problem IN firefox, or is FF crashing a symptom?

sorry for an additional response, but I'm trying to reproduce the crash while in Troubleshoot Mode, as was suggested. This page specifically triggered a whole lot of crashes, so that's why I'm here. I've got YouTube playing in another tab as well. I'm going to copy-paste some of the codes here, they're the same as earlier ones, but sometimes the crashes happened while I was typing or copy-pasting. Here goes. bp-077c1f29-e1d8-4bae-9c7c-46bcf0260913 13/09/2026, 22:41 View bp-26431cfb-22ed-479e-adc3-3e3380260913 13/09/2026, 22:37 View bp-d770d33a-ca67-45dc-855b-f82450260913 13/09/2026, 22:37 View bp-d5edea27-c8d9-47ad-b0d9-376910260913 13/09/2026, 22:37

and here's some copy-paste from the computer logs. libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/radeonsi_drv_video.so JS ERROR: TypeError: this.actor is null _syncEnabled@resource:///org/gnome/shell/ui/windowManager.js:138:25 onStopped@resource:///org/gnome/shell/ui/windowManager.js:150:35 _makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:150:22 _easeActorPrope

well, that didn't trigger anything either.

By the way, I did open Troubleshoot Mode at some points in yesterday's attempts to fix things, and it still crashed yesterday in TM. But today it isn't. beginning to think that yeah, it's not FF itself. probably.

My computer temperature has historically been really, really hot. But today, and yesterday, it was fine and cool. I had some issues with the fans because my two cats have been shedding like mad. Also my power cable noped out after about four years of continuous abuse, but I have a new one attached now. Really shoulda shopped around, I paid through the nose for a new charger since it's 300W.

Still no crashes, but that's absence data and not solid proof. Either way, I'll keep y'all updated. Maybe tomorrow I'll try to check the hardware status. I'd feel a little silly if it just turned out an ant crawled into the RAM and died there or something, lol.

Nope, that's perfectly fine. To put it into some perspective — no two crashes were the same, and each and every one makes you either unique on the whole planet, or, say one of three, four people/devices crashing in the same spot during the past 7 days — which usually means it's as random as it gets, and there's no reason why the crash occurred at that particular spot. Systemic issues aside (read: Raptor Lake material degradation), the reasons are usually faulty RAM modules, or OS–level things (GPU driver bug and the like).

Maybe the right question is… is that a recent change? Would it make sense to run something like mozregression and feed it a range of versions, and see if there's any difference in stability over time?

progress report: have been busy. yesterday I had three FF crashes (one crashed the computer too) and one startup failure. this morning I opened up the case to check for any obvious signs of failure/damage and it looks alright to my inexperienced eyes. I took the chance to clean out lingering dust and crumbs as well. next I will run a memory test when I have the chance.

if the mods want, since I've probably(?) ruled out FF as the *source* of the problem, the thread can be marked solved or closed or whatnot...

Hi Astra, nice picture, this is before you cleaned? Our furry friends are very good at clogging vents. I the pic I can see some of the fins on the RH fan are clogged, as is the vent outlet on the LH side. Search 'clogged laptop fan' checkout images. Heat kills computers, electrolytic capacitors dry out and vent, so there performance will gradually degrade. Search 'vented motherboard capacitor' Hope jbr is able to further guide you. Good Luck 🍀

the photo is from midway, I pulled out the extra hair from the fans and used a soft paintbrush to remove fine dust from crevices.

good news and bad news: I ran a test of my RAM and it passed with flying colours. works perfectly. good to learn about the various kinds of hardware degredation to watch for.

I'll try out mozregression to see if it makes any difference. And I'll keep searching the computer logs for clues what to investigate next.

Good Work Astra, did you see how the gunk builds up at the fan output abutted to the heatsink input under the cover?