Search Issue Tracker
Fixed
Fixed in 6000.0.56f1, 6000.2.1f1, 6000.3.0a5
Votes
0
Found in
6000.0.54f1
6000.1.12f1
6000.2.0b10
6000.3.0a2
Issue ID
UUM-112637
Regression
Yes
ArgumentException is thrown and textures become unreadable when AssetBundle.Unload(false) is called
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/TestLoadTextureFromBundle.unity“ Scene
3. Enter the Play Mode
4. Observe the Console window
Expected result: No errors are thrown
Actual result: “ArgumentException: Texture2D.GetPixels: texture data is either not readable, corrupted or does not exist” error is thrown
Reproducible with: 6000.0.49f1, 6000.0.54f1, 6000.1.12f1, 6000.2.0b10, 6000.3.0a2
Not reproducible with: 6000.0.48f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
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
- Text cursor remains visible when hovering over Command Line Arguments scrollbar in Unity Hub
- UI Builder’s "Background" icons for Repeat Y/X, Position X/Y and Slice Type are low quality and blurry in the Inspector window
- “X” button in Editor version search filter is difficult to see when Unity Hub theme is set to Dark
- [Android] The y-value of Input.mouseScrollDelta is positive when scrolling in both directions in the Player
- Crash on TexturesD3D11Base::SetTexture when using DirectX11
Resolution Note (fix version 6000.3.0a5):
Fixed an issue where calling AssetBundle.Unload(false) on a bundle containing a texture that was already loaded would make it unreadable.
Resolution Note (fix version 6000.2.1f1):
Build Pipeline: Fixed an issue where calling AssetBundle.Unload(false) on a bundle containing a texture that was already loaded would make it unreadable.
Resolution Note (fix version 6000.0.56f1):
Build Pipeline: Fixed an issue where calling AssetBundle.Unload(false) on a bundle containing a texture that was already loaded would make it unreadable.