Open Bug 1322097 Opened 8 years ago Updated 1 years ago

Unsubmitted/unsent crash reports are ignored on linux

Categories

(Toolkit :: Crash Reporting, defect, P2)

Product:
Toolkit
Component:
Crash Reporting
Version:
53 Branch
Platform:
x86_64
Linux
Type:
defect

Tracking

()

People

(Reporter: euthanasia_waltz, Unassigned)

Details

STR: 1. Ensure ~/.mozilla/firefox/Crash Reports/pending is empty 2. Start firefox 3. Visit https://twitter.com/firefox and scroll several pages 4. Exit firefox 5. Make sure ~/.mozilla/firefox/Crash Reports/pending is not empty (if it is empty, repeat step 2-4) 6. Start firefox ER: "You have an unsent crash report" notification appears, about:crash shows Unsubmitted Crash Reports AR: Nothing both In pending folder, there are 3 files such as 0fa6924b-6ee2-49e5-034734b4-2177e031-browser.dmp 0fa6924b-6ee2-49e5-034734b4-2177e031.dmp 0fa6924b-6ee2-49e5-034734b4-2177e031.extra IMO, this file name(id part) violates UUID pattern. https://dxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/CrashReports.jsm#44 https://dxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/CrashSubmit.jsm#30 If I renamed it to 0fa6924b-6ee2-49e5-0347-34b42177e031, then expected results come. This occurs on LinuxMint 18 and Manjaro Linux 16.10, but not on Windows 10.
Component: Untriaged → Breakpad Integration
Product: Firefox → Toolkit
Severity: normal → S3
Severity: S3 → S2
Priority: -- → P2
Status: UNCONFIRMED → NEW
Ever confirmed: true

As a data point: I'm on Linux with Firefox Nightly 114.0a1 (2023-04-30). I recently had the "You have an unsent crash report" notification come up (incidentally, I've never seen this in my 15+ years of firefox on linux, though that was almost all Stable). I clicked "Always" to send all reports in the future. I also had already enabled "Allow Nightly to send backlogged crash reports on your behalf" in the settings. About 5 hours later, I checked about:crashes and the crash report was still unsubmitted (at which point I manually submitted it, which worked).

You need to log in before you can comment on or make changes to this bug.