![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
128.1.0 Nebula crash overnight every night.
128.1.0 Nebula crash overnight every night.
Все ответы (6)
What are your crash IDs listed at Help > Troubleshooting Information?
In re: "What are your crash IDs" When I check it shows "No crash reports have been submitted." I am guessing this means nothing will show here unless you submit a crash report? If not, is there someplace to find the crash reports or submit crash reports after the fact? My instance of thunderbird is reliably (?) crashing every night. I login to my computer each morning to be greeted by the "Thunderbird has crashed" requester. I'm running 64 bit thunderbird portable on windows 11 if that matters.
So, I just restarted thunderbird after this mornings crash and went to get the version string and was greeted by a "updating now" message (it is now "128.2.0esr 64-bit"). So, it seems the version that was crashing for me has been updated to a new version. I guess I'll see if I have a crash message tomorrow. ¯\_(ツ)_/¯
Wayne Mery said
Please see https://support.mozilla.org/en-US/kb/mozilla-crash-reporter-tb
Thunderbird cannot create the crash record due to an error (see attached) which says:
Thunderbird Crash Reporter
Thunderbird had a problem and crashed. Unfortunately, the crash reporter is unable to submit a report for this crash.
Details: Failed to move D:\tbportable-64bit\Data\profile\minidumps\2c7e1474-c831-45c7-8d3f-5ae576e7a336.dmp to C:\users\vern\AppData\Roaming\Thunderbird\Crash Reports\Pending\2c7e1474-c831-45c7-8d3f-5ae576e7a336.dmp
I noticed that in my "C:\Users\vern\AppData\Roaming\Thunderbird\Crash Reports" folder, I do not have a "pending" subfolder but instead have an "events" folder. I use thunderbird Portable. Could the lack of a "Crash" folder be the reason the crash reporter is unable to write the crash report?
Изменено
I think your crash is likely to be https://bugzilla.mozilla.org/show_bug.cgi?id=1891962. This not yet a fix for it, nor a workaround.
The failure to submit the crash report is likely https://bugzilla.mozilla.org/show_bug.cgi?id=506009 - fixed in 130, not fixed in 128.