Search Issue Tracker

Third Party Issue

Votes

0

Found in

2021.3.30f1

2022.3.10f1

2023.1.14f1

2023.2.0a14

Issue ID

UUM-52915

Regression

No

Crash at ScriptingInvocation::Invoke when invoking class constructor from an unmanaged native DLL

-

How to reproduce:
1. Open the attached project "DLL_Test.zip"
2. Enter Play Mode

Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.14f1, 2023.2.0a14
Not reproducible with: 2023.2.0a15, 2023.2.0b11, 2023.3.0a6

Reproducible on: Windows 11 22H2
Not reproducible on: No other environment tested

First lines of stacktrace:
0x000001bdbfc13947 (Mono JIT Code) (wrapper managed-to-native) object:wrapper_native_00007FFB59B51311 ()
0x000001bdbfc13129 (Mono JIT Code) [Mangled.cs:67] Mangled:loadNative ()
0x000001bdbfc12e43 (Mono JIT Code) [Mangled.cs:113] Mangled:Start ()
0x000001be2287e958 (Mono JIT Code) (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr)
0x00007ffad29efb54 (mono-2.0-bdwgc) [mini-runtime.c:3445] mono_jit_runtime_invoke
0x00007ffad292e794 (mono-2.0-bdwgc) [object.c:3066] do_runtime_invoke
0x00007ffad292e92c (mono-2.0-bdwgc) [object.c:3113] mono_runtime_invoke
0x00007ff725ecd174 (Unity) scripting_method_invoke
0x00007ff725eacab4 (Unity) ScriptingInvocation::Invoke
0x00007ff725e9c54e (Unity) MonoBehaviour::InvokeMethodOrCoroutineChecked

  1. Resolution Note:

    It looks like this is a problem in the native library from the project.

Add comment

Log in to post comment