Firefox tabs keep crashing saying... ---------------------------------------------------
Gah. Your tab just crashed.
We can help!
Choose Restore This Tab to reload the page. ---------------------------------------------------
Search for the above message leads to...
https://askubuntu.com/questions/966332/ddg#966361
[
Problem solved.
Had to go: in Location enter: about:config
Type in filter box: browser.tabs.remote
Set both settings to false: browser.tabs.remote.autostart = false browser.tabs.remote.autostart.2 = false
Restart Firefox.
No crashing after that.
--Ziggy Witkowski ]
But, no luck, Firefox tabs still crash.
Any help would be much appreciated.
On Sat, 10/31/2026 2:20 AM, Adam wrote:
Firefox tabs keep crashing saying...
---------------------------------------------------
Gah. Your tab just crashed.
We can help!
Choose Restore This Tab to reload the page.
---------------------------------------------------
Search for the above message leads to...
https://askubuntu.com/questions/966332/ddg#966361
[
Problem solved.
Had to go: in Location enter: about:config
Type in filter box: browser.tabs.remote
Set both settings to false: browser.tabs.remote.autostart = false browser.tabs.remote.autostart.2 = false
Restart Firefox.
No crashing after that.
--Ziggy Witkowski ]
But, no luck, Firefox tabs still crash.
Any help would be much appreciated.
Your posting makes no indication of the Firefox version.
But... your UserAgent in the header is... interesting.
I know you can spoof that field (I do), but still...
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
Tabs should not crash. Usually, the movie player task can crash,
and it is happy to crash, because the main task just forks
another helper.
Regular tab-handling task (there are a variable number of them),
they should not be crashing. Either the web page content is
attempting to use an exploit (stack smashing), or alternately,
you have bad RAM in the computer. And we know that is not the
case, because you don't mention any other Ring 3 programs
crashing.
If you really are running some older version of Firefox,
that potentially doesn't have the stack smashing detection
code in it. As an example of how the versions of Firefox may
differ.
You should:
1) Have two Ubuntus.
2) Have a Daily Driver, "as you like it". Maybe it's ESR and
you've been using it for ten years.
3) Have a second Ubuntu with a "current" OS install and a Firefox 159.0
(four days ago) to test the web sites in question. This boot choice,
would allow you to repeat such a test, with a known-good vintage of code.
If you think some code is corrupted, you can ask the package
manager to reinstall the executable. It can unpack the package
cache file and do a reinstall with it.
There are various ways to make portable versions of programs.
Just make sure the design is such it does not "migrate" your
Daily Driver version you are preserving.
While you could attach a debugger, dealing with a multi-process
executable is not my idea of fun and I don't even know of a good
way to handle the tab-handling cohort. You need to know enough
so that when the debugger (gdb maybe) hits an exception, there
should be a command which "dumps a stack trace" for the exception.
Like if there were seven Firefox processes and three of them
were tab-handlers, you need some way to attach to those three,
and have maybe three copies of gdb and three terminal windows.
Then in one of the windows, you will see an update indicating
an exception has occurred and then you can dump the stack
and get the names of routines.
When the routine names change on every crashed tab-process,
that means it could be a RAM problem. If it crashes in exactly
the same place each time, it means the web site is trying
to tip you over with some code.
That's hardly a lot to go on, and I've *never* debugged
one of these, not ever. Anything with seven processes and
a main process and six children, that's outside my payscale.
*******
One problem with comparing Firefox 38.0 to Firefox 159.0 ,
is the code the web site serves to those two browsers is
entirely different. This foils the attempt to do comparisons.
If this is a redirect attack and a rogue site, then chances
are it will be a lot more successful at what it does on
an older Firefox, than a newer Firefox.
You can't be on Firefox 38, you should be on something >52.x .
As otherwise the Tab could not restart. It takes Quantum, to
support a tab restart. Which is somewhat greater than 52.x .
Paul
Firefox tabs keep crashing saying...
Thanks, GURU Paul !!
This problem started after I used System Monitor to end the Firefox process. Probably not a good idea (20/20 hindsight).
Using about:config to change configuration settings seem to make things worse.
Maybe I have too many tabs open ?!?!?-a Trying to close some now.-a Trying to easy stuff before I attempt the more difficult ones suggested by GURUs.-a :-)
On Sat, 10/31/2026 5:05 AM, Adam wrote:
Thanks, GURU Paul !!
This problem started after I used System Monitor to end the Firefox process. Probably not a good idea (20/20 hindsight).
Using about:config to change configuration settings seem to make things worse.
Maybe I have too many tabs open ?!?!? Trying to close some now. Trying to easy stuff before I attempt the more difficult ones suggested by GURUs. :-)
I don't see the connection, but I've run into a few threads
where a Media setting in about:config, is being used to correct
a Gah tabs crashing problem. This should not be the case.
https://support.mozilla.org/eu/questions/1563602 <=== click the translate option, to get English
"about:config" in the address bar,
search for "media.wmf.vp9.enabled", <=== this sounds like a *Windows* setting... the wmf part
and set its value to false.
That should be a selection to cause the *movie decoder*
to stop crashing.
Some NVidia video cards decode VP8, some decode VP9, never
seem to decode both. Presumably the movie negotiation process,
the web site can get some sort of info about what movie
formats are supported. Some movies are presented as "HTML5"
but I don't know what that implies regarding codec choices.
A Tab can have a movie in it. They're frequently used for
advertising. On Linux, a choice of a VP8 or VP9 video
is workable. For them to offer an MP4, would likely
have some costs associated with it. MP4 should play on
all ecosystems that have Firefox.
This is a stretch as a root cause, and the whole idea
of process isolation, was precisely so that a movie
could not take down a tab.
Other possible settings (not seen in threads so far),
are things like disabling hardware acceleration, but then
that would likely just kill the browser if that was the
problem. Maybe the parent, while drawing windows, suffers
blowback from the video card.
Web extensions are supposed to be sandboxed in a separate
process, so those should not really take down a tab. But
then, we don't know how well shielded these things are.
If a subsystem caused some sockets to fail, that can be
interpreted as a dead process, which will get a child killed
by the main process and a new child forked. Whether that
should be labeled as Gah your tab crashed, I don't know what
the policy is. There is a difference between a tab that crashes
on its own, and a tab that was gunned down by the parent.
On the first release of Firefox with parent and children, the
handling of sockets and child states was poor. It did not take
then too long to fix that. What was happening back then, is
Firefox shutdown was pretty slow. Even though the architecture
has some merit to the ideas of isolation, how you handle
sockets and "failures to respond", that is not an exact science,
as the parent has few mechanisms to measure the real actual
health of the child. Just because the process is not responding,
does not mean it is toast. It might be an issue purely with
the socket. A child could freeze due to a thread deadlock
inside the child.
Paul
On 2026-10-31 03:20 AM, Adam wrote:
Firefox tabs keep crashing saying...
That's why I don't update to the latest "anything" unless I have to.
I'm running obsolete software top to bottom and everything works great.
If it ain't broke, don't fix it. :-D
On 10/31/2026 09:38 PM, Paul wrote:
On Sat, 10/31/2026 5:05 AM, Adam wrote:
Thanks, GURU Paul !!
This problem started after I used System Monitor to end the Firefox
process. Probably not a good idea (20/20 hindsight).
Using about:config to change configuration settings seem to make
things worse.
Maybe I have too many tabs open ?!?!? Trying to close some now.
Trying to easy stuff before I attempt the more difficult ones
suggested by GURUs. :-)
I don't see the connection, but I've run into a few threads
where a Media setting in about:config, is being used to correct
a Gah tabs crashing problem. This should not be the case.
https://support.mozilla.org/eu/questions/1563602 <=== click the
translate option, to get English
"about:config" in the address bar,
search for "media.wmf.vp9.enabled", <=== this sounds
like a *Windows* setting... the wmf part
and set its value to false.
Just set "media.wmf.vp9.enabled" to false, Close and Restart Firefox,
switch to a different tab and get the message... ----------------------------------------------------------------------
Sorry. We just need to do one small thing to keep going.
Firefox has just been updated in the background. Click Restart Firefox
to complete the update.
We will restore all your pages, windows and tabs afterwards, so you can
be on your way quickly. ----------------------------------------------------------------------
I notice the checks for Human or Bot causing problems for browsers,
which constantly require updates. Argh!
That should be a selection to cause the *movie decoder*
to stop crashing.
Some NVidia video cards decode VP8, some decode VP9, never
seem to decode both. Presumably the movie negotiation process,
the web site can get some sort of info about what movie
formats are supported. Some movies are presented as "HTML5"
but I don't know what that implies regarding codec choices.
A Tab can have a movie in it. They're frequently used for
advertising. On Linux, a choice of a VP8 or VP9 video
is workable. For them to offer an MP4, would likely
have some costs associated with it. MP4 should play on
all ecosystems that have Firefox.
This is a stretch as a root cause, and the whole idea
of process isolation, was precisely so that a movie
could not take down a tab.
Other possible settings (not seen in threads so far),
are things like disabling hardware acceleration, but then
that would likely just kill the browser if that was the
problem. Maybe the parent, while drawing windows, suffers
blowback from the video card.
Web extensions are supposed to be sandboxed in a separate
process, so those should not really take down a tab. But
then, we don't know how well shielded these things are.
If a subsystem caused some sockets to fail, that can be
interpreted as a dead process, which will get a child killed
by the main process and a new child forked. Whether that
should be labeled as Gah your tab crashed, I don't know what
the policy is. There is a difference between a tab that crashes
on its own, and a tab that was gunned down by the parent.
On the first release of Firefox with parent and children, the
handling of sockets and child states was poor. It did not take
then too long to fix that. What was happening back then, is
Firefox shutdown was pretty slow. Even though the architecture
has some merit to the ideas of isolation, how you handle
sockets and "failures to respond", that is not an exact science,
as the parent has few mechanisms to measure the real actual
health of the child. Just because the process is not responding,
does not mean it is toast. It might be an issue purely with
the socket. A child could freeze due to a thread deadlock
inside the child.
Paul
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:49:38 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |