Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2021.3.3f1
2022.1.3f1
2022.2.0a13
Issue ID
UUM-2394
Regression
No
Custom Project freezes when entering Play mode, reloading the project and exiting it
How to reproduce:
1. Open the attached 'project-1262412.zip' project
2. Enter and Exit the Play mode
3. Re-load the project
4. Close the Editor
Editor freezes
Reproducible with: 2019.4.8f1, 2020.1.2f1, 2020.2.0a12
Could not test with: 2018.4.26f1 (the project crashes upon loading), 2020.2.0a13, 2020.2.0a20 (the Weathermaker asset is using deprecated methods and the project won't compile)
Comments (1)
-
Bzuco
Aug 10, 2020 20:55
In case it will be hard to reproduce, here is video http://bzucko.sk/weatherMakerExitUnity.mp4
For me last working version without issue was 2019.2.21.
In never versions(2019.3.x, 2019.4.x) editor freezes.What helped me is defragment RAM memory each time after closing editor(not recorded in video). Then I was able close editor without freezing in next session. Without defragmenting RAM memory, editor freezes again in next session.
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Thank you for bringing this issue to our attention. We could not reproduce this on currently supported versions. If you think you can still reproduce it, feel free to log another bug and please continue to log any further issues you may find.
Resolution Note (2022.2.X):
Thank you for bringing this issue to our attention. We could not reproduce this on currently supported versions. If you think you can still reproduce it, feel free to log another bug and please continue to log any further issues you may find.