You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @bb107, Here's another issue I found with MemoryModulePP
I did dig into it and found some clues, So if load a module which uses RTTI (Run-Time Type Information) then Free the module and Load a new modified one it throws std::error on RTTI type conversion and says Access Violation - No RTTI data!
I tracked down the issue and found out it's causing only by usage of
VirtualFree(mod, 0, MEM_RELEASE);
At BOOL MemoryFreeLibrary(HMEMORYMODULE mod) which called
if (!MemoryFreeLibrary(BaseAddress)) __fastfail(FAST_FAIL_FATAL_APP_EXIT);
I'm not sure what is happening but I guess new loaded module allocated memory is some how conflicting with freed memory space?
The text was updated successfully, but these errors were encountered:
Hi @bb107, Here's another issue I found with MemoryModulePP
I did dig into it and found some clues, So if load a module which uses RTTI (Run-Time Type Information) then Free the module and Load a new modified one it throws std::error on RTTI type conversion and says
Access Violation - No RTTI data!
I tracked down the issue and found out it's causing only by usage of
At
BOOL MemoryFreeLibrary(HMEMORYMODULE mod)
which calledif (!MemoryFreeLibrary(BaseAddress)) __fastfail(FAST_FAIL_FATAL_APP_EXIT);
I'm not sure what is happening but I guess new loaded module allocated memory is some how conflicting with freed memory space?
The text was updated successfully, but these errors were encountered: