Hi,
I have had similar problems using an MFC app and MFC dll. The problem is that both have their own memory tracker. Memory allocated in the app and freed in the dll (vice versa) will trigger this error since the memory handle to be freed is not known in the dll's memory objects list. This is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.