Closed Bug 895246 Opened 7 years ago Closed 3 years ago

Many duplicate reports for some B2G signatures

Categories

(Socorro :: General, task)

x86
macOS
task
Not set

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: marcia, Unassigned)

References

Details

While looking at B2G crash data, it seems there is a pattern of dupes with this signature:

https://crash-stats.mozilla.com/report/list?product=B2G&signature=liboemcamera.so@0x116bc

There seems to be a pattern of uptime is repeated in many of the reports, but it seems they are not getting picked up has dupes - the pattern I see for uptime is 8149, 107, 29.
Today the dupe count on a different signature has grown to 667 literally overnight:

https://crash-stats.mozilla.com/report/list?product=B2G&signature=liboemcamera.so@0x12494

Is there anything that would account for the fact we are getting a sudden spike in duplicate crashes?
http://bit.ly/1aBLpit shows up at the top of B2G crashes and is a signature that is all dupes - 1778 crashes.
Summary: Duplicate reports for some B2G signatures are not recognized → Many duplicate reports for some B2G signatures
Some of the uptimes are different.
The same time might be when the user connected to Internet via Wi-Fi, thus all stored crash reports are submitted in a row. It might also be a bug in the B2G code when the Wi-Fi connection is on progress (no hysteresis threshold) duplicating artificially a single crash.
I don't think it's a Socorro bug but instead a B2G one.
Scoobi is right.

I was able to replicate the situation via:
1) flashing and not having the device connected to wifi
2) crashing
3) waiting for the device to restart b2g
4) rebooting
5) waiting for the device to come back up and then connect to wifi

-rw-r----- root     root           49 2013-10-02 11:37 bp-12d4e54b-a033-472e-b3b8-009bb2131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-1fd526ef-5ef7-4a44-8d31-b0bee2131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-30e26817-7ce4-4d27-9fbe-fb2e32131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-33bb18c6-6524-49be-9662-2d6de2131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-692dcd2a-3126-4647-bf26-35ca82131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-a1ccc591-a1ea-4bbc-8940-94b9f2131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-b4e5f1bf-ef83-4f93-a64c-a5b0e2131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-db6286b3-dad7-43d4-b1f7-c54a52131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-e16685fa-44c9-451b-9269-ff47c2131002.txt
-rw-r----- root     root           49 2013-10-02 11:37 bp-e5157f08-2321-485c-a4a3-062692131002.txt
root@android:/data/b2g/mozilla/Crash Reports/submitted # 


I am unsure if there was only one minidump or multiple.  I'll have to see if I can replicate again.
It doesn't seem to happen to all crashes, using the kill -11 command to kill with the STR doesn't seem to trigger the multiple crash reports.

Not sure how to do step 2 so that it will crash reliably and show duplicate reports consistantly yet.
Not supporting b2g any more.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.