Search Issue Tracker
Fixed in 2017.3.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
0
Found in
2017.2.0b3
Issue ID
930354
Regression
Yes
Editor crashes at BlobWrite::TransferBasicData<int> when opening scene
Steps to reproduce the crash in Unity 2017.3 and 2017.2:
1. Download project from provided link (OwnCloud)
2. Open "Locomotions" scene (Assets->Scene)
3. Editor crashes
Steps to reproduce the crash in Unity 2017.1 and 5.6:
1. Download project from provided link (OwnCloud)
2. Open "Locomotions" scene (Assets->Scene)
3. Enter and exit play mode
4. Close project
5. Open Project
6. Editor crashes
Results: Editor crashes in Unity 2017.3 and 2017.2 when opening scene. In Unity 2017.1 and 5.6 Editor crashes when reopening project
Note: The only way how to open Locomotion scene is to open any other scene and enter and exit play mode. Locomotions scene still crashes when entering play mode
Reproduced with: 2017.2.0b3, 2017.2.0a2, 2017.1.0p2
Not reproducible with: 5.6.0a5
Regression introduced in: 5.6.0a6
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
- The alpha blending of transparent objects rendered to a RenderTexture is not rendered correctly in the Game View when in Play mode
- Scrolling on a default ScrollView in a WebGL build is too sensitive when compared to other platform builds and the Editor
- "Fix All" button does not disappear after applying fixes when setting up DXR
- Custom ScriptableObject asset in the project setting are not well deserialized during the Reimport All process
- Fixing Message Loss in UMPE During Domain Reload
shubhamswaraj2021
Aug 18, 2020 15:59
good one <a href="https://www.lyricsauto.com">lyricsauto</a>