Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2021.2.X, 2022.1.X
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.5f1
2022.1
Issue ID
1385611
Regression
No
Windows Standalone Player build exits with non-zero code when scripting backend set to IL2CPP
Reproduction steps:
1. Open project "shutdown-test.zip"
2. Open Build Settings window in File > Build Settings
3. Change platform to Windows Standalone Build and enable the Development Build option, Copy PDB files option, Script Debugging, and Wait for Managed Debugger
4. Build and Run Scene "Test" (pop up will appear, don't close it)
5. Open Visual Studio and press "continue without code"
6. Go to Debug > Attach Unity Debugger, then select shutdown-test with type: player
7. Close the pop-up and observe Visual Studio Console
Expected result: No exceptions are thrown
Actual result: Exceptions are thrown
Reproducible with: 2019.4.34f1, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2
Error: The thread 0x98569ab0 has exited with code 0 (0x0).
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2022.2):
Fixed in: 2022.2.0a5
Resolution Note (fix version 2022.1):
Fixed in: 2022.1.0b8
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.11f1