Search Issue Tracker
Fixed
Fixed in 2021.3.37f1, 2022.3.22f1, 2023.2.14f1, 6000.0.0b11
Votes
0
Found in
2022.2.21f1
2022.3.5f1
2023.1.16f1
2023.2.0b11
2023.3.0a7
6000.0.0b11
Issue ID
UUM-48520
Regression
Yes
Non power of 4 BC1 texture fallback code can lead to a crash with some textures
Observed in VRChat with a 2019-built 2x2 BC1 texture. The fallback code truncates the number of mips from 3 to 2 which puts the texture at a size (20B) which then leads to a some memory getting corrupted which causes a crash on free.
Likely reproducable with a 2x2 BC1 texure with 3 mips being loaded into a 2022.3 player and hitting the fallback code.
We haven't been able to manufacture a standalone repro project for this, although the pre-build bundle that
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 6000.0.0b11):
Since the compressed data in such small textures is actually larger than the uncompressed data, memory corruption was observed. This has been fixed.