Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2017.4.X, 2018.4.X, 2019.1.X, 2019.2.X
Votes
4
Found in
2019.1.0a10
2019.2.0a1
2019.2.0a8
Issue ID
1137077
Regression
Yes
Editor silent crash when attempting to load a new Scene after allocating data
Steps to reproduce:
1. Open QA-supplied project ("Link in the description")
2. Open Scene ("Launcher")
3. Enter Play mode
4. Press: Top-most right button, left-most bottom button, bottom right button.
5. Wait
Reproduced in: 2019.1.0a10, 2019.2.0a8, 2019.2.0a9
Not reproduced in: 2017.4.24f1, 2018.3.10f1, 2018.3.0a9
Note: If you remove new Scene loading from the Generation script, the crash no longer happens.
Note: 2019.1.0a1-2019.1.0a9 throws "UnityException: get_streamingAssetsPath can only be called from the main thread.
Constructors and field initializers will be executed from the loading thread when loading a scene."
Managed to strip the project from 2Gb to 80mb, deleting more impacts the reproduction
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
- NullReferenceException when setting 'isTextObjectScaleStatic' to false on a disabled TextMeshPro GameObject
- Shader Stripping Custom Options disappear when exiting Play mode without reloading Domain
- Decals do not get projected when 'Rendering Layer Mask' on a GameObject is 23rd Layer or above due to encoding/decoding issues
- Deriving from SearchContextAttribute doesn't always work
- Scripting API documentation is missing for macOS editor extensions
Resolution Note (fix version 2019.3):
Fixed in 2017.4.31f1, 2018.4.4f1, 2019.1.9f1, 2019.2.0b7, 2019.3.0a7