My dev team found a strange problem with VirtualAllocEx function after calling this function from 32bit binary but the HANDLE to hProcess was a 64bit process (actually this was a bug we didn't see in the past). VirtualAllocEx succeedes and returns a
valid pointer but calling VirtualFreeEx does not free this memory. This doesn't happen on a PC without latest Windows 10 updates.
Any ideas?
Thanks.
Moved byDave PatrickMVPFriday, August 3, 2018 12:23 PMnot reporting forums profile issues