What happens if you download from Mozilla to a separate folder and run it?

https://www.mozilla.org/en-US/firefox/all/#product-desktop-release

I was running on my distro's version for sometime, but keep losing tabs and have been running it separately for about a month now with no issues.

Operating System: openSUSE Tumbleweed 20210107 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.10.4-1-default OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600

What happens if you download from Mozilla to a separate folder and run it? https://www.mozilla.org/en-US/firefox/all/#product-desktop-release I was running on my distro's version for sometime, but keep losing tabs and have been running it separately for about a month now with no issues.

seems to have done it so far. it got me thinking, does firefox have a theoretical upper-limit for tabs? i've got 1500 open, wondering if that's the issue. maybe earlyoom?

edit: it isn't oom

Are you currently using a version from the repositories of your Linux distribution? Try the Firefox version from the official Mozilla server:

https://www.mozilla.org/en-US/firefox/all/

bp-7e418e46-b201-45c7-a7c9-313840210111 Signature: libxul.so@0x2a480a5 | libxul.so@0x40e763e

MOZ_CRASH Reason (Sanitized) : failed printing to stderr: Input/output error (os error 5)

Crash Reason SIGSEGV /SEGV_MAPERR

this doesn't work. exact same issue whether i use official builds or not

Firefox from the (Fedora) repositories doesn't come with crash symbols, so it isn't possible to check the crashing thread in the report.

Do you have a crash report of Firefox from the Mozilla server to see if that gives usable information about the crashing thread ?

report from the official build is bp-89e11536-8771-40c5-ad8d-a87e00210112

when the next crash happens, i'll try restarting with an i/o redirection to /dev/null. sounds stupid, but i've had a similar issue with steam

Do you get useful messages if you start Firefox via a terminal window ?

You can create a new profile as a quick test to see if your current profile is causing the problem.

See "Creating a profile":

• https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

• https://support.mozilla.org/en-US/kb/recovering-important-data-from-an-old-profile

Have you tried running a trace to see when Firefox is crashing?

cor-el: no useful terminal output. profiles did not change anything

jonzn4suse: no idea how to do that and i don't feel like setting up gdb for more info

anyway, i've been running for several hours now without crashing with this command: `firefox > /dev/null 2>&1`. looks like redirecting stderr was the issue after all. why my system has had this issue multiple times now is a mystery, i guess i'll open a redhat bugzilla thread

The following examples stores the strace output(o option)to firefox_txt file with time stamps(t option)on each line.

strace -to firefox_txt firefox

unfortunately the strace attempt locked up my machine and i had to hard reset. looks like strace doesn't handle that many tabs very well haha

and just like that, the issue has stopped. maybe it was the reboot that fixed it?