You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Mike Balfour 0ae123eae6 Fix AssetContainer behavior with immediate load errors ... The AssetContainer was getting "stuck" in the case that it tried to load a missing asset that was already registered with the AssetManager as missing. This fixes the bug, as well as adding a unit test for the specific condition.		5 years ago
..
AssetCommon.cpp	Disable weak references and unit tests for them.	5 years ago
AssetDataStreamTests.cpp	Initial commit	5 years ago
AssetManagerLoadingTests.cpp	disable AssetJobsFloodTest.ContainerCoreTest_BasicDependencyManagement_Success test (#703)	5 years ago
AssetManagerStreamingTests.cpp	Fix AssetContainer behavior with immediate load errors	5 years ago
BaseAssetManagerTest.cpp	Initial commit	5 years ago
BaseAssetManagerTest.h	Initial commit	5 years ago
MockLoadAssetCatalogAndHandler.h	Initial commit	5 years ago
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.	5 years ago