Search Issue Tracker

Active

Votes

0

Found in

2022.3.66f1

6000.0.57f1

6000.2.4f1

Issue ID

UUM-117749

Regression

Yes

Crash on do_runtime_invoke when reopening a specific project after failing to build it

-

How to reproduce:
1. Open the attached “IN-114190“ project
2. Navigate to “File > Build Profiles“
3. Select the Windows or the macOS Platform
4. Make sure that the Scene List contains “Scenes/Main“
5. Click on the “Build“ button
6. Wait for the build to complete{color:#ffbdad} {color}with a result of “Failed”
7. Close the project and open it again
8. Observe the crash

Reproducible with: 2022.2.0b5, 2022.3.66f1, 6000.0.57f1, 6000.2.0b2, 6000.2.4f1
Not reproducible with: 2022.2.0b4, 6000.3.0b1
Fixed in: 6000.3.0a1

Reproducible on: MacOS 15.6.1 (M4), Windows 11 (by user)
Not reproducible on: No other environments tested

Notes:
- The “Main“ scene has no GameObjects in the Hierarchy window
- After the crash, reopening the project will result in crashing at launch. It will stop crashing when switching to a different Unity version

First few lines of the stack trace:

{noformat}0x00007ffb5978d254 (mono-2.0-bdwgc) do_runtime_invoke (at C:/build/output/Unity-Technologies/mono/mono/metadata/object.c:3068)
0x00007ffb5978d3cc (mono-2.0-bdwgc) mono_runtime_invoke (at C:/build/output/Unity-Technologies/mono/mono/metadata/object.c:3115)
0x00007ff6847003a4 (Unity) scripting_method_invoke
0x00007ff6846de114 (Unity) ScriptingInvocation::Invoke
0x00007ff6846981ce (Unity) MonoScriptInfoScraper::GetAssemblyScrapedMonoScripts{noformat}

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.