Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
2019.2
2019.3
2019.3.0f5
2020.1
Issue ID
1213005
Regression
No
Crash when creating a new Texture2D with a resolution greater or equal to 2048 and the mipCount higher than 1
How to reproduce:
1. Open the attached project named "Case_1213005"
2. Open the Sample Scene
3. Enter Play mode
Expected result: Editor Enters Play mode and successfully creates a new Texture2D or throws a related error message
Actual result: Editor crashes
Reproducible with: 2019.2.18f1, 2019.3.0f5, 2020.1.0a20
Could not test with: 2017.4.36f1, 2018.4.15f1(Constructor option to set the mipCount was introduced in 2019.2)
Notes:
- Setting the resolution to 1024x1024 and the mipCount to 12 produces the following error:
Assertion failed on expression: 'mipCount >= -1 && mipCount <= fullMipChainCount'
UnityEngine.Texture2D:.ctor(Int32, Int32, GraphicsFormat, Int32, TextureCreationFlags)
NewBehaviourScript:Start() (at Assets/NewBehaviourScript.cs:12)
- The crash can be worked around by passing both the mipcount and TextureCreationFlags.MipChain to the Texture2D constructor.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2020.1):
Crash is fixed along with an extra error logged if the mipcount passed in is too high.
Fixed in Unity 2020.2.0a2
Resolution Note (fix version 2019.4):
Fixed in - 2019.4.29f1