863998 - No placeholder for 8 digit hex addresses within Java signatures since April 11

Status: RESOLVED FIXED

(Socorro :: Backend, task)

Description

[Scoobidiver (away)]

The feature of bug 726385 disappeared on April 10 at 23:30. See https://crash-stats.mozilla.com/report/list?range_value=4&range_unit=weeks&signature=android.view.WindowManager%24BadTokenException%3A%20Unable%20to%20add%20window%20--%20token%20android.os.BinderProxy%40%3Caddr%3E%3A%20is%20not%20valid%3B%20is%20your%20activity%20running%3F%20at%20android.view.ViewRootImpl.setView%28ViewRootImpl.java%29

It's again a regression in Socorro 41.

Comment 1

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

Pull Request 1194 addresses this problem. 

If I search the socorro database for instances of this problem, I find 1420 instances since 4-10. 
 
* Do you want these crashes reprocessed?  
* If reprocessed, should materialized views / aggregate reports be regenerate all the way back to 4-11?
* Does this fix warrant a point release or can the fix wait until our next scheduled release?

Comment 2

[Scoobidiver (away)]

(In reply to K Lars Lohn [:lars] [:klohn] from comment #1) 
> * Do you want these crashes reprocessed?
yes.
> * If reprocessed, should materialized views / aggregate reports be
> regenerate all the way back to 4-11?
yes.
> * Does this fix warrant a point release or can the fix wait until our next
> scheduled release?
The next release is fine as those crashes are not top crashers and long standing issues.

Comment 3

[Robert Kaiser]

I think reprocessing at least a week back is probably a good idea, I don't think we need to backfill for it, though.

Comment 4

[[github robot]]

Commit pushed to master at https://github.com/mozilla/socorro

https://github.com/mozilla/socorro/commit/14065a7bcea1ba776513afc73770cc65197d2a20
Merge pull request #1194 from twobraids/java-place

fixes Bug 863998 - updated newprocesor java sig utilities to match old