1851898 - Try harder to include JavaStackTrace (and maybe also JavaException) annotations in crash reports

Status: NEW

(Fenix :: Crash Reporting, task, P2)

Description

[Chris Peterson [:cpeterson]]

Bug 1847429 comment 24 says:

There are still 7,101 Fenix crash reports since 2023-08-01 which have "EMPTY: no frame data available". I spot checked those and they don't have a JavaStackTrace annotation, a JavaException annotation, or a minidump

Bug 1847429 comment 27 says:

JavaException is ... a bit of a misnomer. It's actually a stack trace, just in a different format compared to JavaStackTrace. Anyway, I feel like the remaining fixes need to happen in Fenix' crash handler. We can close this bug as fixed and open a new one in Fenix crash handler to make sure it tries harder to populate at least one of the two annotations.

TBD: Should crash reports include both JavaException and JavaStackTrace annotations? Or prefer JavaException? Bug 1792902 asks if we should retire JavaStackTrace now that we have JavaException.

Comment 1

[Chris Peterson [:cpeterson]]

Answer: we should include at least JavaStackTrace and maybe also JavaException.

willkg says in bug 1851903 that:

1. He and Roger spec'd out and implemented the structured JavaException annotation which is far superior to JavaStackTrace in a variety of ways.
2. But there are multiple things in Socorro that still depend on JavaStackTrace.

By including both JavaStackTrace and JavaException now, we will have an easier transition path for moving Socorro from JavaStackTrace to JavaException later.