Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.1.X, 2018.2.X
Votes
8
Found in
2017.2.0b9
Issue ID
946976
Regression
Yes
PersistentManager::ReadObject crash when exiting Unity if VSCode plugin is installed
To reproduce:
1. Open users attached project "RaycastPlatformer.zip"
2. Navigate to VSCode > Plugins > Editor
3. Save the project
4. Close the editor with the x in the top right
Expected result: Unity closes
Actual result: Unity crashes
Reproduced on: 2017.2.0b5 2017.2.0b9 2017.2.0f1 2017.3.0b1
Not reproduced on: 5.6.3p3 2017.1.1p2 2017.2.0a1 2017.2.0a4
Regression introduced in: 2017.2.0b1
VS Code plugin is not required for VS Code support in Unity 2017.2. So the workaround for this issue is to uninstall the VS Code plugin and just use the built-in support instead.
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
enhawk
Jan 09, 2018 08:29
Hi this is still happening in 2017.3
alimoeeny
Nov 21, 2017 14:27
Also you don't need to navigate to VSCode or anything, as long as you have it installed editor crashes.
alimoeeny
Nov 21, 2017 14:26
If you bring some other application to the foreground and close Unity Editor (mac) by other means, like right click on the icon in the task bar or using activity monitor or something, then Unity will not crash on exit.
Still true as of 2017.3.0b10