Skip to content

Failing to capture native crashes on Windows #1620

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bitsandfoxes opened this issue Apr 15, 2024 · 0 comments · Fixed by #1622
Closed

Failing to capture native crashes on Windows #1620

bitsandfoxes opened this issue Apr 15, 2024 · 0 comments · Fixed by #1622
Assignees
@bitsandfoxes
Labels
Bug Something isn't working Native Platform: Windows

Comments

@bitsandfoxes
Copy link
Contributor

Originally raised on discord

The SDK fails to capture native crashes triggered through Utils.ForceCrash(ForcedCrashCategory.Abort); on the current LTS (2021.3.37f1, 2022.3.24f1)
Other relevant crashes are

AccessViolation
FatalError
Abort

It looks like these Unity versions overwrite our backend. We've attempted to reinstall the backend in this PR. That fixes the issue for C SEGFAULTS and FatalError but does not help with C++ exceptions. Turns out we're reinstalling the backend too early and the input system overwrites some of the handlers again.
We need to find a place to reliably re-install the sentry backend. (i.e. before/after the splashscreen?)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bitsandfoxes bitsandfoxes

Labels
Bug Something isn't working Native Platform: Windows
Projects
GDX
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: Reinstall backend to capture native crashes getsentry/sentry-unity
1 participant
@bitsandfoxes