Search Issue Tracker
Duplicate
Votes
0
Found in
5.6.0f3
Issue ID
899857
Regression
No
Unity crashes when "scale" value for spawning child elements is set to small numbers
Repro steps:
1. Open provided projects "scene0" scene
2. Select "Ground" -> "HOLDER" in the hierarchy
3. Change the scale to: a) (1;1;1) this makes it crash for me
b) (0.005;1;0.005) this makes it crash for the user
4. Enter play mode (If it doesn't crash, exit play mode and enter it again until Unity crashes)
Expected: For Unity not to crash
Actual: Unity crashes
Reproduced with: 2017.1.0b1, 2017.1.0a6, 5.6.0f3, 5.5.3f1
Can't reproduce with: 5.4.5f1
Note:
Different values that you set for the "HOLDER" scale, seem to crash different computer, because for me it only crashes when the scale is set to (1;1;1) and for the user only when the number is small (like <0.1)
Also added crash.dmp and error.log files
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
This is a duplicate of issue #892396