Search Issue Tracker

Fixed in Unity 2018.3

Votes

8

Found in

2017.2.0b9

Issue ID

946976

Regression

Yes

PersistentManager::ReadObject crash when exiting Unity if VSCode plugin is installed

Serialization

-

-

Priority: 3Not yet prioritized for a release

-

Severity: 1Crash, freeze, data loss, work stops

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)

  1. C4d29d31ffc653e07ea79f4014272de7?d=mm

    hawken

    Jan 09, 2018 08:29

    Hi this is still happening in 2017.3

  2. 9e8dd06976ead4082d2181f3807117e1?d=mm

    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.

  3. 9e8dd06976ead4082d2181f3807117e1?d=mm

    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

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.