Sentry 3.2.0, 3.2.1 and 3.2.2 cause a crash on certain nvidia platforms

[pdyatlov]

Environment

Nvidia gefore rtx 3070 + latest drivers
DirectX11

How did you install the package? (Git-URL, Assetstore)
Add package

Which version of Unity?
6000.0.47f1

Is this happening in Unity (editor) or on a player like Android, iOS, Windows?
Build

Steps to Reproduce

1. Install Sentry 3.2.0
2. Load a scene (can send a test build by request)
3. The game crashes with EXCEPTION_ACCESS_VIOLATION_READ / 0x58
4. Note: game does NOT crash with 3.1.0 and earlier

Any logs or screenshots

Captured crash for reference: https://white-ink.sentry.io/issues/43477493/?project=4507232130105424&query=is%3Aunresolved%20issue.priority%3A%5Bhigh%2C%20medium%5D&referrer=issue-stream&stream_index=3

By the native debug callstack, that's the name of the crashing dll (sentry.dll):

sentry-unity/src/Sentry.Unity/NativeUtils/CFunctions.cs

Line 80 in cc4a467

[DllImport("sentry")]

[bruno-garcia]

Thanks for reporting this.

Does it crash in launch?
any specific code that triggers it? thinking how we can repro it in our side.
Looking at the changelog I can't immediately see what change could be triggering this https://github.com/getsentry/sentry-unity/releases/tag/3.2.0

we'll need to diff 3.2.0 and 3.1.0 the version before.

[pdyatlov]

The crash comes from the nvidia driver, I'm not sure if it's related to code at all. I have the game on Steam, I can upload it to a testing branch and give you the password so you can repro it on your machine

The game crashes when I launch the main scene

[bruno-garcia]

Diff: 3.1.0...3.2.0

The game crashes when I launch the main scene

Hm perhaps its due to: SceneManager.GetActiveScene().name)

added in:

• The SDK now reports the active scene's name as part of the Unity Context (2084)

Googling (gives me a gemini answer)

Could you try an empty game and calling SceneManager.GetActiveScene().name) to see if that triggers it?

[pdyatlov]

Just double checked,

1. Calling SceneManager.GetActiveScene().name does NOT trigger a crash
2. Loading another scene does NOT trigger a crash
3. Only loading a scene with specific objects (code?) causes it