Memory corruption due to FSkeletalMeshMerge::GenerateLODModel writing out of bounds in certain cases
I was having memory corruption after running FSkeletalMeshMerge::DoMerge on certain mesh combinations (caused TBBMalloc to crash on random new allocations) so i ran the engine with the stomp debug allocator, now it reliably crashes here:
the problem is the VertData write out of bounds, i is 356 because it goes from 0 to NumVertices (391) however the array size is only 354 (since thats the size of DupVertData). There is some faulty logic here that determines that number of vertices, since DupVertIndexData is indeed sized 391, but DupVertData is not.
asked Jul 03 '19 at 04:43 AM in Bug Reports
This was fixed in https://github.com/EpicGames/UnrealEngine/commit/3c281c4ca5289802b741050f81117b88a52868ee#diff-4307661913a7b8476f50603ebd8eb3e1 It just never made it into release.
Always good when master is MORE STABLE than release.
answered Jul 03 '19 at 04:55 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here