Search Issue Tracker

Fixed

Fixed in 6000.0.63f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a5, 6000.5.0a1

Votes

2

Found in

6000.0.60f1

6000.2.8f1

6000.3.0b7

6000.4.0a3

Issue ID

UUM-122776

Regression

No

Crash when you call UnloadAllAssetBundles and there are pending AssetBundle.UnloadAsync tasks

-

Description:
UnloadAllAssetBundles will unload all the AssetBundle waiting for any pending load operation, but it won't wait for any unload operation on the AssetBundle itself. Due to that, the bundle will be unloaded while the unload operation is still pending, and when the operation executes it will crash because the bundle has already been unloaded.

How to reproduce:
1. Open the attached “IN-121566.zip” project
2. Click on Test > Build Bundles in the toolbar
3. Open the “SampleScene”
4. Enter Play Mode
5. Observe the crash

Reproducible in: 2023.1.0a1, 6000.0.60f1, 6000.2.8f1, 6000.3.0b7, 6000.4.0a3

Reproducible on: Windows 11
Not reproducible on: No other environments tested

First few lines of stacktrace:
0x00007FF9187B9095 (Unity) GetAssetBundlePrefix
0x00007FF9187B8899 (Unity) GetAbsoluteAssetBundlePrefix
0x00007FF9187A4885 (Unity) AssetBundleUnloadOperation::GetAssetBundleAbsolutePathPrefix
0x00007FF9187A5E4A (Unity) AssetBundleUnloadOperation::Perform

  1. Resolution Note (fix version 6000.5.0a1):

    Fixed crash when you call UnloadAllAssetBundles and there are pending AssetBundle.UnloadAsync tasks.

  2. Resolution Note (fix version 6000.4.0a5):

    Fixed in 6000.4.0b5

  3. Resolution Note (fix version 6000.3.0b10):

    Fixed crash when you call UnloadAllAssetBundles and there are pending AssetBundle.UnloadAsync tasks.

  4. Resolution Note (fix version 6000.2.12f1):

    Fixed crash when you call UnloadAllAssetBundles and there are pending AssetBundle.UnloadAsync tasks.

  5. Resolution Note (fix version 6000.0.63f1):

    Fixed crash when you call UnloadAllAssetBundles and there are pending AssetBundle.UnloadAsync tasks.

Comments (4)

  1. llFlexford

    Nov 24, 2025 09:56

    Why didn't fixed for Unity 2022.3.62?

  2. llFlexford

    Nov 05, 2025 12:58

    Please fix also for Unity 2022.3.62f2

  3. llFlexford

    Oct 27, 2025 19:56

    ========== OUTPUTTING STACK TRACE ==================

    0x00007FF6D8FE595A (Unity) GetAssetBundlePrefix
    0x00007FF6D8FE5163 (Unity) GetAbsoluteAssetBundlePrefix
    0x00007FF6D8FD46C5 (Unity) AssetBundleUnloadOperation::GetAssetBundleAbsolutePathPrefix
    0x00007FF6D8FD6DBE (Unity) AssetBundleUnloadOperation::Perform
    0x00007FF6D87D8055 (Unity) PreloadManager::ProcessSingleOperation
    0x00007FF6D87D888E (Unity) PreloadManager::Run
    0x00007FF6D87D891A (Unity) PreloadManager::Run
    0x00007FF6D895FBFB (Unity) Thread::RunThreadWrapper
    0x00007FF9D846E8D7 (KERNEL32) BaseThreadInitThunk
    0x00007FF9D9D8C53C (ntdll) RtlUserThreadStart

    ========== END OF STACKTRACE ===========

  4. llFlexford

    Oct 27, 2025 18:25

    I have the same issue on Unity 2022.3.62f2 with addressables 1.28.0

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.