1693693 - figure out java crash signature algorithm

Status: NEW

(Socorro :: General, task, P3)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

Now that we have a structured stack, we can do a better job with signature generation for Java crashes.

This bug covers figuring out the use cases and then designing an algorithm for that.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

I'm doing the planning work in this doc:

https://docs.google.com/document/d/1VUqiulo-NoAouz8XHfOuvEqyHAZCL6P3z5LOPISZmYM/edit#

Comment 2

[Will Kahn-Greene [:willkg] ET needinfo? me]

Bumping bugs off my queue because I'm not going to get to them any time soon.

Comment 3

[Will Kahn-Greene [:willkg] ET needinfo? me]

I started working on this. Here's my notes:

While working on bug 1847429, I implemented the beginning of a signature generation overhaul for Java signatures.

I was thinking along these lines:

1. If we want to support sentry events, we'll want to use the "exception" structure. However, JavaException value has the stacktraces and frames ordered differently than Sentry does. So we'll need to normalize them if/when we support Sentry events generally. There are bugs for that.
2. There are a number of bugs that get fixed when we switch to using JavaException.
3. We'll want to change the structure to EXCEPTION | FRAME | FRAME | FRAME so it matches C signatures.
4. We should look at how we normalize frame signatures. Some of them are really long because Java classes and methods are long strings.

Many of the people I wanted to talk with about Java signatures are gone now. Chris Peterson said to talk with him and RyanVM. They triage crashes. I should also talk with Gabriele and Roger.

One thing to think about is the big disruption in signatures changing. We need to factor that into the plan. Chris said something about writing a script.

Chris also said most Fenix engineers don't like Socorro and continue to look at crash data on Sentry. We should find out why. Maybe we can improve the interface.

Next step is to finish up the proposal.

https://docs.google.com/document/d/1VUqiulo-NoAouz8XHfOuvEqyHAZCL6P3z5LOPISZmYM/edit