Grouping of issues differs depending on mechanism

[adinauer]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Send in a Java exception with a cause from v7 and v8 of Java SDK.

Throwable ex = new RuntimeException("outer exception", new ArithmeticException("cause (inner exception)"));
Sentry.captureException(ex);

Expected Result

Both exceptions should show up on the same issue in Sentry.

Actual Result

Two separate issues are created in Sentry.

• v7: https://sentry-sdks.sentry.io/issues/6504347301/?project=5428563&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&sort=date&stream_index=1
• v8: https://sentry-sdks.sentry.io/issues/6220732148/?project=5428563&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&sort=date&stream_index=3

Main difference I was able to spot is that we're now sending mechanism in v8 and did not in v7:

"mechanism":
{
    "type": "chained",
    "exception_id": 1,
    "parent_id": 0
}

... parent ...
"mechanism":
{
    "type": "chained",
    "exception_id": 0
}

Product Area

Issues

Link

No response

DSN

No response

Version

No response

[armenzg]

If you look download the JSON events and look at the diff of the stack traces, you will see there are various frames that are different.

[adinauer]

In "Event Grouping Info | Grouping" the difference is the order of exceptions.
The difference you mentioned is very likely just because we upgraded some dependencies in the sample between v7 and v8.