mbalfour 5df82caef6 [LYN-3464] Vegetation unit tests intermittently failed due to an AssetManager bug. Inside the AssetContainer, if the root asset finished loading during the container initialization, the CheckReady() call at the end of initialization would detect the loaded asset, but would skip sending out notifications because the initialized flag wasn't set yet. This would lead to an extra asset reference remaining in the AssetManager itself, would would then cause errors when the asset handler for that asset got removed. ...

By setting the initialization flag before the CheckReady() call, the notifications get sent correctly, and no extra asset references remain.  This checkin also includes a unit test for the AssetManager that specifically forces this condition to happen and validates that it works correctly.

2021-05-04 09:04:18 -05:00

..

AssetCommon.cpp

Disable weak references and unit tests for them.

2021-04-22 15:02:41 -05:00

AssetDataStreamTests.cpp

Initial commit

2021-03-08 14:30:57 -08:00

AssetManagerLoadingTests.cpp

Add jira ticket for disabled tests

2021-04-23 10:50:58 -05:00

AssetManagerStreamingTests.cpp

[LYN-3464] Vegetation unit tests intermittently failed due to an AssetManager bug. Inside the AssetContainer, if the root asset finished loading during the container initialization, the CheckReady() call at the end of initialization would detect the loaded asset, but would skip sending out notifications because the initialized flag wasn't set yet. This would lead to an extra asset reference remaining in the AssetManager itself, would would then cause errors when the asset handler for that asset got removed.

2021-05-04 09:04:18 -05:00

BaseAssetManagerTest.cpp

Initial commit

2021-03-08 14:30:57 -08:00

BaseAssetManagerTest.h

Initial commit

2021-03-08 14:30:57 -08:00

MockLoadAssetCatalogAndHandler.h

Initial commit

2021-03-08 14:30:57 -08:00

TestAssetTypes.h

[LYN-3464] Vegetation unit tests intermittently failed due to an AssetManager bug. Inside the AssetContainer, if the root asset finished loading during the container initialization, the CheckReady() call at the end of initialization would detect the loaded asset, but would skip sending out notifications because the initialized flag wasn't set yet. This would lead to an extra asset reference remaining in the AssetManager itself, would would then cause errors when the asset handler for that asset got removed.

2021-05-04 09:04:18 -05:00