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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
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.