Are you using the rpm or something else, e.g. Mozilla’s binary, a flatpak or snap?
With firefox-104.0.2-1.fc36 I see that error message, but Firefox is rock-solid.
If you really want to run v106, you can try one of the COPRs that carry it, or use the nightly build from Mozilla.
In that case, it may be worth checking if it’s not a red herring, following the instructions here. If you do pinpoint another issue, you should file a bug.
There is a possibility that it’s due to changes in the net gear on my LAN. My Marvell Clearfog Pro running Arch Linux Arm bit the dust on a software update. In general 32-bit support for Linux is dying and it’s an armv7. I had to switch to my backup router. The Clearfog Pro was running Pi-Hole directly on the router on bare metal. My backup router is running OpenWRT and it doesn’t have enough RAM to run Pi-Hole so I’m now running Pi-Hole in a podman container on a laptop on a shelf with the case closed (“mini-server”). I have to go out and buy new network cables to get the router off of the floor. It’s been rough because I have so many projects including switching to a new Google Pixel 6a. On top of everything I got my fourth COVID vaccination (Moderna bivalent) two days ago and it was a doozy.
If Pi-Hole is somehow interfering with the remnants of the Firefox updater, it might be the case. You could very easily (???) connect directly to your router and see if you still get the crashes.
In any case, thank you so much for the photo, it made my day