Re: [Iup-users] IUP 3.29 Possible leak at iupwin_open.c

De: Ranier Vilela Enviado: quinta-feira, 25 de junho de 2020 21:01 Para: IUP discussion list. Assunto: Re: [Iup-users] IUP 3.29 Possible leak at iupwin_open.c >Interestingly, I don't call this function directly, anywhere. >I am using the IUP-3.27 release libraries. The call origin i

Re: [Iup-users] IUP 3.29 Possible leak at iupwin_open.c

De: Antonio Scuri Enviado: quinta-feira, 25 de junho de 2020 20:59 Para: IUP discussion list. Assunto: Re: [Iup-users] IUP 3.29 Possible leak at iupwin_open.c > Ok, I'll check. But why iupwinShowLastError is being called? It is not > called by any IUP function... It is there for >

Re: [Iup-users] IUP 3.29 Possible leak at iupwin_open.c

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

[Iup-users] IUP 3.29 Possible leak at iupwin_open.c

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