Search Issue Tracker


Fixed in 2020.3.45f1, 2021.3.19f1, 2022.2.6f1, 2023.1.0b3, 2023.2.0a1



Found in





Issue ID




"AssetBundle is invalid" and "Failed to decompress data" errors appear after building and loading large LZMA Asset Bundle



How to reproduce:
1. Open project “”
2. In the Project window select the “089-our-lady-of-the-hour-church.fbx” file (Assets > Data)
3. Go to Menu > AssetBundle > Export AssetBundle
4. In the Hierarchy window select "BundleLoader" GameObject
5. In the Inspector window right-click on the "Asset Bundle Loader" script Component and press "Load Bundle"
6. Observe the Console window

Expected result: No errors
Actual result: "AssetBundle is invalid" and "Failed to decompress data for the AssetBundle" errors appear

Reproducible with: 2019.4.40f1, 2020.3.36f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a17, 2023.1.0a3

Reproduced on: macOS 11.6 (Intel), Windows 10

Note: The 3rd step might take some time to export because the file is ~2GB

Further details from testing the repro: This is a Windows AssetBundle Build, with the AssetBundle being loaded in the editor.
The AssetBundle is LZMA compressed and 2.41 GB (2,592,996,026 bytes)
On Andrew laptop it takes 2minutes 15 seconds before it fails with "Failed to decompress data for the AssetBundle '089-our-lady-of-the-hour-church.assetbundle'."
Its generated by adding a single FBX that references many png files each 85MB and jpg files each 43MB

*Second repro*: There is a second report, described in the comments of this same ticket. That is a loading bug with the same error message but coming from a much smaller bundle and specific to WebGL. That ticket has been spun off to because it actually is a very different repro scenario and the fix for that won't help the original

  1. Resolution Note:

    Fixed by another internal issue: UUM-22990: Webgl "Failed to decompress data" error when trying to load specific Asset Bundle

  2. Resolution Note (fix version 2023.2.0a1):

    Fixed in: 2023.2.0a1

  3. Resolution Note (fix version 2023.1.0b3):

    Fixed in: 2023.1.0b3

  4. Resolution Note (fix version 2022.2.6f1):

    Fixed in: 2022.2.6f1

  5. Resolution Note (fix version 2021.3.19f1):

    Fixed in: 2021.3.19f1

  6. Resolution Note (fix version 2020.3.45f1):

    Fixed in: 2020.3.45f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.