Closed
Bug 1757938
Opened 3 years ago
Closed 3 years ago
Crash in [@ EMPTY: no crashing thread identified; HeaderMismatch]
Categories
(GeckoView :: General, defect, P3)
GeckoView
General
Tracking
(Not tracked)
RESOLVED
MOVED
People
(Reporter: fluffyemily, Unassigned)
References
Details
(Keywords: crash)
Crash Data
|
||
Comment 1•3 years ago
|
||
Agi says the missing crash data is a crash reporter bug. This crash is not actionable until that bug is fixed.
needinfo'ing Agi because he said he would find a link to the crash reporter bug.
Flags: needinfo?(agi)
Priority: -- → P3
|
||
Comment 2•3 years ago
•
|
||
Just to clarify, I don't think there's any data loss here. I think a bunch of crash reports that used to have signature EMPTY: no crashing thread identified; EmptyMinidump now have signature EMPTY: no crashing thread identified; HeaderMismatch.
It's this issue in android-components: https://github.com/mozilla-mobile/android-components/issues/11809
|
||
Comment 3•3 years ago
|
||
That was fixed about a week ago. Looking at the recent 99.0a1 and 100.0a1 data this is no longer happening. So ideally the crash data is being processed out into the respective crashes.
|
|
||
Updated•3 years ago
|
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → MOVED
You need to log in
before you can comment on or make changes to this bug.
Description
•