Bug Report: GameThread Timeout / RenderThread Deadlock (Windrose-Win64-Shipping)

[arctic mist]

Summary:
Frequent crashes occur during normal gameplay due to the GameThread timing out while waiting for the RenderThread (120s limit). Logs indicate a strong correlation between SkeletalMesh clothing recreation, slow DAL transactions, and a detected memory leak.
Technical Details:
Engine Error: LogRendererCore: Error: GameThread timed out waiting for RenderThread after 120.00 seconds.
Primary Culprits:
UR5MeleeAbility::RemoveEventGEs — frequently called before lockup.
USkeletalMeshComponent::Recreating Clothing Actors — mass recreation of clothing for actors (e.g., SK_Armor_Dogface, SK_ArmorCreature_Drowned) seems to choke the RenderThread.
R5BLDalAsyncQueue — "Slow task" warnings (up to 1080ms) for Commit transactions right before the freeze.
Resource Monitor: R5LogSystemResources reports a suspected memory leak: growth rate ~5.10 Mb/s.
Memory State at Crash: ~11.7 GB Physical used, ~24-25 GB Total System Physical used (out of 32 GB).
Steps to Reproduce (observed):
Play normally for 20–40 minutes.
Engage in combat using Melee abilities.
Observe multiple "Recreating Clothing Actors" and "Actor_Drop_AddRule" events in logs.
Game freezes for 120 seconds and terminates.
Files for Investigation:
Source\R5\Feature\Combat\Ability\Melee\R5MeleeAbility.cpp:828
Plugins\R5BusinessLogicCore\Source\R5BLCommon\Cpp\R5DataAbstractionLayer\R5BLDalAsyncQueue.cpp:1210
Plugins\R5BusinessRules\Source\R5BusinessRules\Cpp\R5Rules\Island\Rules\Drop\R5BLActor_Drop_AddRule.r5bl.cpp:33

[lilac zodiac]

Thanks for the report. What environment are you playing in?

[arctic mist]

I created a summary report using Google's neural network. The reliability of the analysis is questionable.

I hope that my reports will be of some help.