Search Issue Tracker

Third Party Issue

Votes

0

Found in

2021.3.26f1

2022.3.0f1

2023.1.0b19

2023.2.0a4

Issue ID

UUM-39797

Regression

No

Crash on RaiseException when calling MethodInfo.Invoke in an obfuscated DLL

--

-

How to reproduce:
1. Open the user attached “ObfuscatedDLLProject“ project
2. Open the “01 Introduction” scene in the “Packages” folder
3. Select “AnimancerChibi” in the Hierarchy
4. Click the Edit button next to the Springs field in the Inspector
5. Change any of the toggles in the middle of the window
6. Click Apply
7. Observe crash

Reproducible with: 2021.3.26f1, 2022.3.0f1, 2023.1.0b19, 2023.2.0a4
Could not test with: 2023.2.0a5, 2023.2.0a17 (Package not supported)

Reproduced on: Windows 10 (Intel)

First lines of stack trace:
0x00007FFB6723CF19 (KERNELBASE) RaiseException
0x00007FFADDA3064C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\utils\mono-log-common.c:143] mono_log_write_logfile
0x00007FFADDA1C4A2 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:172] monoeg_g_logv_nofree
0x00007FFADDA1C57C (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:215] monoeg_assertion_message
0x00007FFADDA1C5C9 (mono-2.0-bdwgc) [C:\build\output\Unity-Technologies\mono\mono\eglib\goutput.c:231] mono_assertion_message

  1. Resolution Note:

    The obfuscator that is being used is producing invalid IL and therefore this behavior is unavoidable. Use ILVerify https://github.com/dotnet/runtime/blob/main/src/coreclr/tools/ILVerify/README.md to verify validity of obfuscated dlls.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.