Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2018.4.X, 2019.4.X, 2020.1.X
Votes
0
Found in
2019.3.0a10
2019.4
2019.4.1f1
2020.1
2020.2
Issue ID
1257655
Regression
Yes
Crash on GetColorBlockColors when entering Play mode in a specific scene
Reproduction steps:
1. Open the attached project ("1257655.zip")
2. Open "clothing" scene
3. Enter Play mode
Reproducible with: 2019.3.0a10, 2019.3.16f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a16
Not reproducible with: 2018.4.24f1, 2019.3.0a9
First lines of the stacktrace:
0x00007FF7D2FE8D24 (Unity) GetColorBlockColors
0x00007FF7D2FD16AE (Unity) DecompressDXT5Impl<void (__cdecl*)(DXTColBlock const *,Color8888 * const)>
0x00007FF7D2FE7699 (Unity) DecompressNativeTextureFormat
0x00007FF7D308C79E (Unity) HandleDecompression
0x00007FF7D3082944 (Unity) GetImagePixelBlock<ColorRGBAf>
Notes:
- If the provided project is upgraded or downgraded, for Library folder has to be deleted before attempting to reproduce it in another version
- In non-reproducible versions the following error shows up right after entering Play mode:
Cannot access pixel data of compressed texture formats which cannot be partially decompressed (such as Crunch).
UnityEngine.Texture2D:GetPixels()
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
- Animator Controller throws MissingReferenceException after undoing Layer Creation
- Full stack trace is always printed when an exception occurs in an IL2CPP build
- Licensing Client fails to launch when opening Unity Hub (licensing client path is not found)
- Licensing Client fails to launch when opening Unity Hub
- Different custom Shader behavior when GPU Resident Drawer is enabled
Resolution Note (fix version 2020.2):
Crash no longer reproduces from 2020.2.0a17, but from 2020.2.0b2 we added appropriate errors that let the user know that crunch compressed textures can not be accessed from scripts
Resolution Note (fix version 2020.1):
Fixed in 2020.1.9f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.15f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.29f1