Search Issue Tracker
By Design
Votes
0
Found in
2018.1.9f1
2018.2.0b10
Issue ID
1096530
Regression
Yes
An Unhandled Exception is thrown when exiting Unity having VSCode Integration Plugin installed
Repro steps:
1. Open QA attached project "repro_1096530"
2. Close Unity
3. Open the Editor.log
Expected: Unity closes without any exceptions
Actual: An "Unhandled Exception: UnityEngine.UnityException: GetBool is not allowed to be called while application is terminating" is thrown
Reproducible with: 2018.2.15f1, 2018.3.0b9, 2019.1.0a8
Not reproducible with: 2017.4.14f1, 2018.2.0b9
The error:
(Filename: /Users/builduser/buildslave/unity/build/Runtime/Scripting/ScriptingThreadAndSerializationSafeCheck.cpp Line: 85)
Unhandled Exception: UnityEngine.UnityException: GetBool is not allowed to be called while application is terminating.
at <0x00000> <unknown method>
at <0x00000> <unknown method>
at <0x00000> <unknown method>
at <0x00000> <unknown method>
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
- “FocusController has unprocessed focus events.” warnings are thrown after adding iOS, tvOS or visionOS Build Profiles
- Holes and different colors appear on default Tree Materials after applying them to the Tree GameObject and undoing changes
- Error indicating that the Text Asset Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
- Documentation installation shows "Install failed: Validation Failed" when installing Android Build Support module
- Error indicating that the Package Manifest Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
Resolution Note:
This is by design, this is a new error message we have introduced in 2018.2 to catch C# code that is accessing internal C++ systems after shutdown, which can lead to crashes during shutdown.