Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2019.4
2020.1
2020.2
2021.1
2021.1.0b2
2021.2
2022.2
Issue ID
1305962
Regression
No
Editor crashes if Unity is closed in the middle of exporting package
The editor crashes because of closing the editor while exporting a package.
It crashes because we try to access a reference to AsyncReadManager that was already set to null during an earlier call to Application.Shutdown() from TickPackageImport().
Investigation notes and call stacks here:
https://docs.google.com/document/d/1MU7tM7J-D4glUC83AYwpi2aQmUwHomUVYDElhTZh7g8/edit
Steps to reproduce:
1) Create a new project.
2) Add a large number of assets to your project, e.g. by importing a big package from the asset store.
4) Right Click in Project > Export package. Export all assets.
5) Wait for the progress window to display the text "Compressing Package...".
6) Right Click Unity from taskbar > Close the Unity Editor Window.
Actual Result: Editor crashes after the package is exported
Expected result: Editor should not crash on closing the window
Occurring on: 2022.2.0a6, 2021.2.0a1, 2021.1.0b2, 2020.2.2f1, 2020.1.10f1, 2019.4.12f1
Environment: Only on Windows
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Tooltip messages should be presented in human language not in code strings
- [Linux] Editor doesn’t auto reload when an Asset is imported or a Script is changed
- MouseDownEvent is triggered when changing from Scene view to Game view
- "GlobalObjectIdentifierToObjectSlow" returns Null when retrieving "GlobalObjectId" from GameObject inside a Prefab
- Shader is invisible in the Build when using BiRP on Meta Quest 2
Add comment