Closed Bug 1718093 Opened 5 years ago Closed 3 years ago

Firefox crashed. Mozilla Crash Reporter was unusable.

Categories

(Toolkit :: Crash Reporting, defect)

Firefox 89
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: richard.brooklyn85, Assigned: gerard-majax)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0

Steps to reproduce:

Started firefox. Navigated to three websites. These are websites I frequently visit.

System: KUbuntu 21.04. Firefox installed via snap package.

Actual results:

Firefox crashed. This is rare for me.

I wanted to submit the crash, but I could not, as the "Mozilla Crash Reporter" tool was unusable. The text was unreadable it was unclear how to proceed.

I have attached a screenshot.

Expected results:

I should be able to submit a crash through the Mozilla Crash Reporter tool.

Component: General → Crash Reporting
Product: Core → Toolkit

Confirming this, we know there's problems with the crash reporter when used in snap packages

Status: UNCONFIRMED → NEW
Ever confirmed: true

Some more information, which I forgot to update this bug with.

The next day, on my laptop, I got the same graphical glitch (no readable letters), but on the main Firefox window instead. No crash this time, just I was unable to see my bookmarks on the bookmark toolbar so I restarted Firefox immediately. The laptop was unused for a couple of days before this bug was noticed and logged and the first use since this bug was logged showed this behavior.

I have a feeling that an update was probably applied automatically by snap on both machines to the same version. Perhaps whilst Firefox was already live and this triggered the odd behavior. This is, if I'm honest, a hunch.

Hi Gabriele,
Do you happen to know if this issue appeared once Proton was launched or this is a pre-existing issue?

Flags: needinfo?(gsvelto)

This is a pre-existing issue. Snap sandboxing messes up the crash reporter though I haven't yet established what is happening exactly. Probably something with the paths that the crash reporter passes in the environment variables VS the actual paths in the snap-based installation.

Flags: needinfo?(gsvelto)
Severity: -- → S2
Blocks: snap

Alexandre, if this is no longer an issue, can you lower the severity?

Assignee: nobody → lissyx+mozillians

I dont think we have problems with crashreporter anymore?

Gabriele, do you think we could close this?

Severity: S2 → S4
Flags: needinfo?(gsvelto)
Attached image Snapshot

Just tried it out, it's working fine

Flags: needinfo?(gsvelto)
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: