Skip to content

Duplicate Sentry Reports for Native Client Crashes #1045

Open
@Atul767

Description

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Electron SDK Version

4.22.0

Electron Version

27.2.20

What platform are you using?

None

Link to Sentry event

https://jupiter-ct.sentry.io/issues/5977075889/events/d8cb5ff92ddd4fbb9e7bd0380f77df83/?project=1430058 , https://jupiter-ct.sentry.io/issues/5105499169/events/49718a83fe6142b4a727520fb6ce24d8/?project=4506692758077440

Steps to Reproduce

  1. Launch the Native Client from the parent application
  2. Trigger a crash in the Native Client.
  3. Observe the crash being reported in both Sentry projects (one under the parent application, one under the Native Client).

We have observed an issue where the same crash is being reported in two separate Sentry projects:

The parent application's Sentry project (e.g., Jupiter).
The Native Client's Sentry project.
This duplication occurs when the Native Client is launched from the parent application. Both projects log the same crash as separate issues.

Example:
Here are two examples of duplicate issues for the same crash:

Parent Application Sentry Project: [MTKView draw]: Fatal Error: EXC_BREAKPOINT / EXC_ARM_BREAKPOINT / 0x100742e00 — Project: jupiter-ct.
Native Client Sentry Project: EXC_BREAKPOINT: height — Project: ringcentral-video-nc.

Expected Result

  • Prevent the parent application from sending Sentry reports for crashes that originate in the Native Client.
  • Ensure that Native Client crashes are reported only in the Native Client's Sentry project

Actual Result

This duplication occurs when the Native Client is launched from the parent application. Both projects log the same crash as separate issues.

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions