https://bugs.winehq.org/show_bug.cgi?id=49633
--- Comment #3 from Piotr Caban piotr.caban@gmail.com --- (In reply to Paul Gofman from comment #2)
Maybe something in game depends on memory being "properly" self overwritten by memcpy within the overlapping memory ranges and not correctly moved?
No (before this patch we were already moving the memory in memcpy, also native dlls are working as expected in this regard and it's still possible to reproduce the crash, we also have tests in msvcrt that this is the expected behavior, I didn't test ucrtbase though).