reported via UDN: [Link Removed]
We're encountering some issues when cooking a specific PSD in our game, this happens regularly but not consistently (sometimes cooks will work fine, whilst other times they'll get stuck in a loop forever).
When they get stuck we only get this message, I've tried leaving it running overnight but to no avail.
LogCook: Warning: Cooker has been blocked from saving the current packages for 3480 seconds. LogCook: Display: 1 packages in the savequeue: LogCook: Display: /Game/Animation/_Shared/PrototypeCombat/CombatTest/Data/PSD_CombatTest LogCook: Display: 1 objects that have not yet returned true from IsCachedCookedPlatformDataLoaded: LogCook: Display: PoseSearchDatabase /Game/Animation/_Shared/PrototypeCombat/CombatTest/Data/PSD_CombatTest.PSD_CombatTest
When debugging the cook process all I've been able to assertain is that we reach FPoseSearchDatabaseAsyncCacheTask::OnGetComplete for the offending PSD, the response is Error and it builds the PSD again, then we reach GetCache().Put(...) and the result is Response.Status is OK, we then hit the OnGetComplete (for the same asset) again with Error, when the issue occurs, at some point along the OnGetComplete we enter a ResetSearchIndex() call and (as far as I can see) after that FPoseSearchDatabaseAsyncCacheTask::StartNewRequestIfNeeded is not called again, and the cook gets stuck waiting for the PSD to return.
I've not been able to recreate the issue in an empty project, and whilst trying to debug it, I had a successful cook, once a successful cook happens the issue stops occurring for a few days but then returns if the asset is modified (I'm guessing a DDC put that results in a successful DDC can sometimes happen bypassing the issue)
Do you have any knowlegde of similar issues happening in the past or what could be causing this?
I've tried opening up the asset and can't see anything obviously wrong in it, but I'm not familiar enough with the asset type to see if there's anything wrong, is there something you could suggest to look out for?
Or any suggestions as to how to debug this further once I get the issue to occur again?
There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-262120 in the post.