On a regular basis, flatpak Firefox "had a problem and crashed", "crash reporter is unable to submit a crash report", "application did not leave a crash dump file"
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: hanno.zulla, Unassigned)
Details
Attachments
(1 file)
|
43.86 KB,
image/png
|
Details |
Bildschirmfoto vom 2022-08-29 15-26-57.png
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:104.0) Gecko/20100101 Firefox/104.0
Steps to reproduce:
- Use Firefox 103 and 104 during a typical home office day.
- Keep the laptop with several open Firefox tabs turned on over night
- Return to the home office next morning
Actual results:
On several mornings, I would find the Firefox window closed and a single notification window on the desktop:
"Firefox had a problem and crashed. We'll try to restore your tabs and windows when it restarts. Unfortunately the crash reporter is unable to submit a crash report. Details: The application did not leave a crash dump file."
Expected results:
Firefox should not crash over night.
When it does crash, it should at least report a more helpful error message or a crash dump file.
I have no idea how to debug this or give you a more helpful bug report than "my Firefox repeatedly crashes overnight".
|
Reporter | |
Comment 1•3 years ago
|
||
This is the flatpak version of Firefox, running on Ubuntu 22.04 with snap-Firefox removed and flatpak used instead.
|
||
Comment 2•3 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
|
Reporter | |
Comment 3•3 years ago
|
||
Should add that so far, this always happens during my absence. I haven't seen a Firefox crash or this error message while I'm actually using the computer.
|
|
Reporter | |
Comment 4•3 years ago
|
||
Schroedinger's Firefox - can't tell if my Firefox is dead unless I unlock the computer in the morning.
|
|
Reporter | |
Comment 5•3 years ago
|
||
Problem still persists with version 105.
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Comment 6•3 years ago
|
||
I haven't seen this with Firefox 106 since a while. Possibly, the cause of this has been fixed. Closing this for now.
Description
•