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.
Comments (3)
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
- Popup windows spawn on the incorrect monitor when the Editor is placed near the boundary of scaled monitor next to a monitor with different scaling
- Hidden Tabs do not shift into empty space after closing visible Tabs
- [Android] Application not deployed on a device when "activity-alias" is used in the AndroidManifest
- Shader compile process adds shader ID to the constant buffer name when the word "Globals" is being used in Vulkan
- Audio Mixer Snapshot link to the documentation isn’t working
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