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
Comments (1)
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
- Crash with multiple stack traces when playing video on a render texture with low-end graphics devices
- Circle handle of the Game view scale slider bar disappears when the scale is set to 1x
- Asset Bundles non-deterministic behavior with CRCs and hash when a video has Transcoding enabled and Sprite Atlas has an override option enabled
- [Quality Hackweek] Errors "InvalidOperationException: EnsureRunningOnMainThread can only be called from the main thread" and "NullReferenceException" shown when switching build platforms with Muse Texture package installed
- "Importer(DefaultImporter) generated inconsistent result for asset" warnings are thrown when reimporting the "URP" texture
shubhamswaraj2021
Aug 18, 2020 15:59
good one <a href="https://www.lyricsauto.com">lyricsauto</a>