Search Issue Tracker
Fixed in 2018.3.X
Fixed in 2018.1.X, 2018.2.X
PersistentManager::ReadObject crash when exiting Unity if VSCode plugin is installed
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.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- [macOS] “Input.GetMouseButtonDown” gets set to true when pressing and when releasing the mouse button in the Device Simulator view if "targetFrameRate" is set in the script
- UWP Capabilities are not changed when rebuilding the project
- [Oculus] Lights causing artifacts when Forward+ Rendering is selected
- Game Window Icons are white when in light mode
- Crash on VFXMemorySerializer::StoreObjects when converting to Subgraph Block
Jan 09, 2018 08:29
Hi this is still happening in 2017.3
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.
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