Search Issue Tracker
Not Reproducible
Votes
0
Found in
2017.1.0a4
Issue ID
912721
Regression
Yes
Memory overflow after "Could not open file for read" error when opening the project for the first time after upgrade
To reproduce:
1. Open project http://bugs04.unity3d.com/fogfiles/884196_aravsen7orukr4to/case_884196-PCE.zip (created in 5.5f2)
2. Agree to upgrading the API
3. Notice the error saying that "Could not open file project_name/library/metadata/5f/5f32cd94baa94578a686d4b9d6b660f7 for read"
4. Press "Cancel"
5. Overflow in memory allocator. error and Unity doesn't start
Regression introduced in 2017.1a4
Reproducible with 2017.1a4, 2017.1b5, 2017.1b7, 2017.2a1
Not reproducible with 5.6, 2017.1a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment