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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
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.