758038 - Re-process reports for the fix in Bug 726385

Status: RESOLVED FIXED

(Socorro :: General, task)

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

1. go to https://crash-stats.mozilla.com/topcrasher/byversion/FennecAndroid/15.0a1/7  2. Sort by crash signatures 
3. look at java.lang.IllegalArgumentException: Receiver not registered: org.mozilla.gecko.G

[ Crash Reports for java.lang.IllegalArgumentException: Receiver not registered: org.mozilla.gecko.GeckoConnectivityReceiver@414b2bd0: at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java) ]

https://crash-stats.mozilla.com/report/list?range_value=7&range_unit=days&date=2012-05-23&signature=java.lang.IllegalArgumentException%3A%20Receiver%20not%20registered%3A%20org.mozilla.gecko.GeckoConnectivityReceiver%40414b2bd0%3A%20at%20android.app.LoadedApk.forgetReceiverDispatcher%28LoadedApk.java%29&version=FennecAndroid%3A15.0a1

Expected: it should be like java.lang.IllegalArgumentException: Receiver not registered: org.mozilla.gecko.GeckoConnectivityReceiver@ at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java)

Actual: java.lang.IllegalArgumentException: Receiver not registered: org.mozilla.gecko.G in various single separate crash signatures

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Seems like nightly is the only one and this bug is the only one showing this issue for now based on the fix for bug 726385

Comment 3

[Robert Kaiser]

You won't see any effect from bug 726385 on crashes that have been processed before this landed. Either this is INVALID or you can turn it into a request for reprocessing those signatures - if so, you need to give a time window of crashes to reproduce and other criteria of how those entries can be found in the DB so they can be posted into the reprocessing queue.

Comment 4

[K Lars Lohn [:lars] [:klohn]]

the crash you are referring to (42012765-08cf-4d22-b19c-44c782120517) came into Socorro on May 17th.  The Java signature changes didn't get into production until today, May 23rd.  Only new crashes moving forward will get the signature address make-over.

If you'd like to have older crashes reprocessed, please file another bug listing the criteria that identifies the candidate crashes.

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Morphing bug into a preprocess of Bug 726385 ; from beta 2 push... 4/25?

Comment 6

[Robert Kaiser]

(In reply to Naoki Hirata :nhirata from comment #5)
> Morphing bug into a preprocess of Bug 726385 ; from beta 2 push... 4/25?

Can you give Matt exact criteria of what reports he needs to query for to stick them in the reprocessing query? Product, what to search for in signatures, date range.
And I guess we'll need to backfill the topcrash reports to make those show up there as well, right?

Matt, can you take a look at that?

Comment 7

[Robert Kaiser]

Naoki, since we now have 2 weeks of new data that has been processed with this in place already, do we still need to reprocess older reports at this point?

If so, we need that more exact criteria here. If not, let's just resolve the bug.

Comment 8

[Selena Deckelmann :selenamarie :selena]

Long ago fixed.