If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Crash Reports change signature to EMPTY: no crashing thread identified

RESOLVED INVALID

Status

()

Firefox
General
RESOLVED INVALID
4 years ago
4 years ago

People

(Reporter: Jan Manthay, Unassigned)

Tracking

21 Branch
x86_64
Windows 8
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Comment hidden (empty)
(Reporter)

Comment 1

4 years ago
(i wrote al lot, but it was deleted, i write it again now... please wait)
(Reporter)

Comment 2

4 years ago
Three of my crash reports from january/february changed there dates and signature.

I tried to open them today, an got an "unable to show" error.

Afer opening about:crahes again a liitle bit later, the 3 reports changed there date to today.
I was able to open them now, but the signaure was wrong:
2 show  [@ EMPTY: no crashing thread identified ] 
1 show [@ F406845520___________________________ ] 

There was a correct date and signature in the past, there were from jan/feb (fx 18) and the signature was flash related.

Now date and signatures are wrong, those are the reports:
https://crash-stats.mozilla.com/report/index/3f1ec76e-09c5-491a-b6e6-3456a2130616
https://crash-stats.mozilla.com/report/index/bp-1e05dd04-7078-4fbf-8d1b-a68d72130616
https://crash-stats.mozilla.com/report/index/a2f337f9-a490-44ab-b8f6-e90e22130616

Comment 3

4 years ago
Those crashes are in 18.0 that are no longer maintained.
In addition, an empty crash thread is not exploitable by Mozilla.

Note that the last four figures of the crash ID is the submit date. To prevent a server saturation, only one crash ID out of ten is sent to Mozilla's servers.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.