repeated "Gah. Your tab just crashed."
Categories
(Firefox :: General, defect)
Tracking
()
People
(Reporter: from-mozilla2, Unassigned, NeedInfo)
Details
Specifically, release candidate 2 (firefox-133.0c2.tar.bz2).
I run both firefox-release (132) and firefox-beta (133), with a custom installer to ensure they don't overwrite each other.
Essentially, I have a cron job that manually downloads the latest release in each stream and unpacks it into its own directory. Importantly, this directory is not owned by me, so it's impossible for a running Firefox to overwrite any part of it.
Specifically, it's unpacked into /opt/mozilla/firefox/firefox-133.0c2.linux-x86_64 and /opt/mozilla/firefox/firefox-beta is a symlink pointing at it.
Then when Firefox prompts me that there's an updated version, I just quit Firefox, pivot the symbolic link to point at the new version, and restart Firefox.
I open most Google products in firefox-beta, and "almost everything else" in firefox.
I mention these not because I think they might cause the problem, but rather to demonstrate the extra steps I've taken to prevent them from interfering with each other.
Since I switched the beta stream to 133, it's been crashing repeatedly, between 2 and 20 minutes.
Lastly, all instances of Firefox run in one Linux cgroup that limits memory to 5GB; without this my 8GB PC frequently becomes unusable. Or at least, it did when I instigated this around about Firefox release 77.
That said, it's not constrained for swap usage, so although it sometimes it goes extremely slowly, this shouldn't cause it to crash.
Oh, and even a tab open on bugzilla crashes, so I'm editing this bug in release 132 instead.
(This probably explains how I managed to create a bug with no description section; sorry about that.)
|
||
Comment 4•15 days ago
|
||
submit crash reports and add the id of one of them in a comment.
|
|
||
Updated•15 days ago
|
I've previously uploaded bp-b416c2ab-dffe-4791-9999-68bbf0241124 but it may not show this symptom, as these are tab crashes, not whole-of-Firefox crashes.
about:crashes doesn't show any crashes since that one (roughly 54 hours ago), and before that none for a month.
I have two clients experiencing similar issues. Both updated Firefox to version 133 on Windows 10 and Windows 11 today, and both have encountered crashes at least twice, accompanied by the same error message. This issue affects all tabs, even new ones, and recovery is not possible. In all cases, we had to restart Firefox.
Is there any additional information I can provide? about:crashes shows:
This application has not been configured to display crash reports. The preference breakpad.reportURL must be set.
@demian to aid with bug triage, can you confirm that we're experiencing the same problem, not just something superficially similar?
Did you see exactly the same error message as in the title of this bug report? If not, was it a tab-crash or did Firefox as a whole crash? Was this a one-off or repeating?
Did restarting Firefox (without changing the version) fix the problem?
(Type “about:crashes” into your URL bar and see if there's a crash report around the time you last had a problem. If there is, then that means it's a whole-of-Firefox crash, not just a tab-crash.)
If it was just a one-off, or if it's a whole-of-firefox crash, then it's unlikely to be the same problem; please file a separate bug report.
If you still think it's the same problem, could you please indicate any other differences and commonalities between my and your systems, such as RAM size or enforced memory limit?
This seems to be fixed in 134, so I've pinned 132 as my "prod" version, at least until 134 reaches "release candidate" status.
If you would like me to revert my "beta" to 133 for further testing, please let me know. (Has it reached "release" or "release candidate" status yet?)
Not sure how much trouble it's worth, but you might like to look at anything that was reverted in 134.0b1.
|
|
||
Updated•12 days ago
|
|
||
Comment 9•5 hours ago
|
||
The severity field is not set for this bug.
:kpatenio, could you have a look please?
For more information, please visit BugBot documentation.
|
||
Comment 10•3 hours ago
|
||
Sorry for my late response.
(In reply to Martin K from comment #7)
@demian to aid with bug triage, can you confirm that we're experiencing the same problem, not just something superficially similar?
Did you see exactly the same error message as in the title of this bug report? If not, was it a tab-crash or did Firefox as a whole crash? Was this a one-off or repeating?
I see the exact same message "Gah. Your tab just crashed."
Did restarting Firefox (without changing the version) fix the problem?
Yes
(Type “about:crashes” into your URL bar and see if there's a crash report around the time you last had a problem. If there is, then that means it's a whole-of-Firefox crash, not just a tab-crash.)
There is no crash listed. It says "This application has not been configured to display crash reports. The preference breakpad.reportURL must be set."
If it was just a one-off, or if it's a whole-of-firefox crash, then it's unlikely to be the same problem; please file a separate bug report.
This happend from time to time over the last few days since updating firefox to 133 on Windows. It does not crash the browser completly but rather the active tab states "Gah. Your tab just crashed.", when this happens reloading the tab does not work. Opening a new tab results in "Gah. Your tab just crashed." Any other tab that was open before and had a webpage already loaded just works fine, as long as i dont reload the page you navigate to another webpage. If i do so these tabs aswell crash with "Gah. Your tab just crashed." . To resolve the issue i have to close firefox completly.
If you still think it's the same problem, could you please indicate any other differences and commonalities between my and your systems, such as RAM size or enforced memory limit?
I do not have a enforced memory limit. The RAM Size on both machine where this occueres is 16GB.
Description
•