Search Issue Tracker
Duplicate
Votes
0
Found in
2017.1.0b3
Issue ID
909051
Regression
No
Crash in CalculateObjectBounds while entering the playmode if GameObject.CalculateBounds is used
How to reproduce:
1. Open the attached "ReproProject1" project and "Repro" scene
2. Enter playmode
Expected result: Scene starts playing
Actual result: Crash occurs
Note: GameObject.CalculateBounds was introduced in 2017.1.0a6, so can't reproduce it on earlier (2017.1.0a5) or different major versions (5.6, 5.5). Using GetComponent().mesh.bounds.size doesn't seem to cause the crash.
Reproducible with - 2017.1.0b4, 2017.1.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
- 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
This is a duplicate of issue #909100