Ok, I'll check. But why iupwinShowLastError is being called? It is not called by any IUP function... It is there for debugging purposes only.
The example in FormatMessage doc is quite clear: https://docs.microsoft.com/en-us/previous-versions/aa908810(v=msdn.10) Best, Scuri Em qui., 25 de jun. de 2020 às 17:50, Ranier Vilela <ranier_...@hotmail.com> escreveu: > Hi Scuri, > > DrMemory, still report leak at iupwinShowLastError function. > Error #4: LEAK 264 direct bytes 0x03d1d250-0x03d1d358 + 0 indirect bytes > # 0 replace_RtlAllocateHeap > [d:\drmemory_package\common\alloc_replace.c:3771] > # 1 combase.dll!InternalTlsAllocData +0x33f (0x759dbd30 > <combase.dll+0x10bd30>) > # 2 combase.dll!InternalTlsAllocData +0xc3 (0x759dbab4 > <combase.dll+0x10bab4>) > # 3 combase.dll!CoInitializeEx +0x34 (0x7595b185 > <combase.dll+0x8b185>) > # 4 iup.dll!iupwinShowLastError +0xe5 (0x69adfff6 > <iup.dll+0x8fff6>) > # 5 iup.dll!IupOpen +0x4d4 (0x69aa23e5 > <iup.dll+0x523e5>) > > Now, most interestingly, it is the function he reports that has been > replaced for testing. > AllocateHeap > > Perhaps Microsoft's documentation is wrong and the correct function for > freeing memory allocated by FormatMessage is FreeHeap. > See at: > > https://docs.microsoft.com/en-us/previous-versions/windows/desktop/legacy/aa374721(v=vs.85) > > Can you test, replace LocalFree for FreeHeap? > > I still, can not compile IUP here. > > regards, > Ranier Vilela > > _______________________________________________ > Iup-users mailing list > Iup-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/iup-users >
_______________________________________________ Iup-users mailing list Iup-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/iup-users
