We have 3 different callstacks related to a crash in
FExportArchive::SerializeBulkMeta(UE::BulkData::Private::FBulkMetaData&, FBulkDataCookedIndex&, long long&, int) (AsyncLoading2.cpp:2779).
From the callstack, the crash can originate from Nanite::FResources::Serialize() (from a StaticMesh / SkeletalMesh) or FDistanceFieldVolumeData::Serialize (from a StaticMesh).
I do not have the names of the related assets unfortunately.
They have been reported by Sentry on a Shipping build, and they have not yet been reproduced by our QA.
I did not find any related thread on EPS or a potential fix on Github, hence I’m asking for some support here, as I don’t have any idea how to tackle this issue.
I searched our internal DB and could only find 1 fix that should already be in version 5.6.0 (CL#42412670). Do you have more details than those stacks?
This look like a CPU crash and doesn’t appear related to the GPU. It’s likely a race condition that results in memory corruption or an overwrite.
I’m not sure what you get from a Sentry report but the state of all threads could be useful. The info usually makes it in CrashContext.runtime-xml but the stacks would not be resolved which wouldn’t help…
The stacks are inconclusive as none is showing activity that could indicate memory overwrite. You should review the custom classes in your project and make sure that you are not missing a UPROPERTY tag on UObject pointers. Untagged references are often linked to this type of problems.