unfortunately after a couple of hours of fun the problem manifests itself again, attached the new crash file.
EA Staff (Retired)@Ruon-21, this is a crash I haven't seen before. Thanks!
There are two addresses to consider:
0x00007FF7BD29FCE0 -- this is the address of the function we wanted to call.
0x40007FF7BD29FCE0 -- this is the address we actually tried to call.
Under 64-bit Windows, memory addresses starting with 0x4 are invalid, so Windows says you got a memory access violation at address 0xFFFFFFFFFFFFFFFF. This is a magic address that the OS reports whenever there is a memory violation you can detect just by looking at the memory address without even trying to look at the memory that the address points to. An analogy would be the post office recognizing that you put a haiku instead of a recipient address on an envelope, so they don't even bother putting it on a truck to find the house.
You'll notice that the only difference between the correct address and the address we tried to call is that the first digit is a 4 instead of a 0. In binary, that's a single bit difference. I don't know any way that the code that fills in this memory could toggle that bit, so it suggests that some other random code is changing that bit behind our back. This sort of bug is really hard to fix without a repro case and/or lots of crash reports.
Community Manager
