Search Issue Tracker
Fixed in 2020.2.X
Votes
1
Found in
2019.3.0b7
2019.4
2020.1
2020.2
2020.2.0a13
Issue ID
1251591
Regression
Yes
[Linux] Assertion failed errors are occasionally thrown when reordering GameObjects in the Hierarchy window
Reproduction steps:
1. Open a new or an existing project
2. Add a few GameObjects to the Hierarchy window there are none
3. Drag a GameObject from the top of the Hierarchy list to the bottom
4. Repeat until an error in the Console window pops up
Expected result: No errors occur in the Console
Actual result: Assertion failed error is thrown occasionally
Reproducible with: 2019.3.0b7, 2019.4.0f1, 2020.1.0b11, 2020.2.0a13
Not reproducible with: 2018.4.23f1, 2019.3.0b6
Note: Not reproducible on macOS or Windows
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
Resolution Note (fix version 2020.2):
Fixed in version 2020.2.0a16