Search Issue Tracker

Won't Fix

Votes

0

Found in

2022.3.57f1

6000.0.37f1

6000.1.0b5

6000.2.0a2

Issue ID

UUM-96497

Regression

No

Crash on operator delete[] when Instantiating an Asset Bundle that references an another Asset Bundle with a MonoBehaviour

-

Reproduction steps:
1. Open the attached user's project "UnityTest_2022"
2. Build and Run the project
3. In the Player, Load Bundles 1, 2, 3
4. Instantiate 1, 2, 3
5. Destroy 1, 2, 3
6. Unload Bundles 2 and 3
7. Load Bundles 2 and 3
8. Instantiate 1, 2, 3

Expected result: The Assets get Instantiated and are visible in the Scene
Actual result: The Player crashes when Instantiating the 3rd Asset

Reproducible with: 2022.3.57f1, 6000.0.37f1, 6000.1.0b5, 6000.2.0a2

Reproducible on: Windows 11 (User), MacOS 15.2 (Intel)
Not reproducible on: No other environment tested

Stacktrace:
#0 0x000001145dcc91 in operator delete[](void*, std::nothrow_t const&)
#1 0x000001145dd4fe in operator delete[](void*, std::nothrow_t const&)
#2 0x00000113bad850 in operator delete[](void*, std::nothrow_t const&)
#3 0x00000113badc65 in operator delete[](void*, std::nothrow_t const&)
#4 0x0000011386e372 in (Unknown)
#5 0x00000113db4efd in operator delete[](void*, std::nothrow_t const&)
#6 0x00000113dde3a6 in operator delete[](void*, std::nothrow_t const&)

  1. Resolution Note:

    Unloading an asset bundle that serves as a dependency for other asset bundles still in use can lead to undefined behavior. This includes serialization errors that may occur even if the dependency asset bundle is later reloaded. To avoid such issues, ensure that an asset bundle and all asset bundles that depend on it are unloaded together.

    we are updating api docs and manual to clarify the usage.

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.