Hi all,
anybody know what causes this leak?
Block 1 08ba9758 (size 40) WMNOTIFY(0) ...
TIA
Ingo
In order for this site to work correctly we need to store a small file (called a cookie) on your computer. Most every site in the world does this, however since the 25th of May 2011, by law we have to get your permission first. Please abandon the forum if you disagree.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
Para que este foro funcione correctamente es necesario guardar un pequeño fichero (llamado cookie) en su ordenador. La mayoría de los sitios de Internet lo hacen, no obstante desde el 25 de Marzo de 2011 y por ley, necesitamos de su permiso con antelación. Abandone este foro si no está conforme.
X3 memory leaks
-
ignacio
- Site Admin
- Mensajes: 9253
- Registrado: Lun Abr 06, 2015 8:00 pm
- Ubicación: Madrid, Spain
- Contactar:
X3 memory leaks
Ingo JH escribió el vie, 05 abril 2013 08:48Hi all,
anybody know what causes this leak?
Block 1 08ba9758 (size 40) WMNOTIFY(0) ...
TIA
Ingo
Hello,
Check if in any part of your code you are trapping the WM_NOTIFY Windows message. In case not try to isolate when the memory leak appears and comment some parts of the code until it disappears.
BTW, try to run the program with absolutely no break points an see if the memory leak persists.
Regards,
anybody know what causes this leak?
Block 1 08ba9758 (size 40) WMNOTIFY(0) ...
TIA
Ingo
Hello,
Check if in any part of your code you are trapping the WM_NOTIFY Windows message. In case not try to isolate when the memory leak appears and comment some parts of the code until it disappears.
BTW, try to run the program with absolutely no break points an see if the memory leak persists.
Regards,
X3 memory leaks
Ignacio,
solved.
Thank you.
Regards
Ingo
"Ignacio Ortiz de Zúñiga" <nonametoavoidspam@xailer.com> schrieb im
Newsbeitrag news:515e75d9$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Ingo JH escribió el vie, 05 abril 2013 08:48
>> Hi all,
>>
>> anybody know what causes this leak?
>>
>> Block 1 08ba9758 (size 40) WMNOTIFY(0) ...
>>
>> TIA
>>
>> Ingo
>
>
> Hello,
> Check if in any part of your code you are trapping the
> WM_NOTIFY Windows message. In case not try to isolate when
> the memory leak appears and comment some parts of the code
> until it disappears.
> BTW, try to run the program with absolutely no break points
> an see if the memory leak persists.
>
> Regards, --
> Ignacio Ortiz de Zúñiga
> [Equipo de Xailer/Xailer team]
> http://www.xailer.com
> http://www.xailer.info
solved.
Thank you.
Regards
Ingo
"Ignacio Ortiz de Zúñiga" <nonametoavoidspam@xailer.com> schrieb im
Newsbeitrag news:515e75d9$[email=1@svctag-j7w3v3j....]1@svctag-j7w3v3j....[/email]
> Ingo JH escribió el vie, 05 abril 2013 08:48
>> Hi all,
>>
>> anybody know what causes this leak?
>>
>> Block 1 08ba9758 (size 40) WMNOTIFY(0) ...
>>
>> TIA
>>
>> Ingo
>
>
> Hello,
> Check if in any part of your code you are trapping the
> WM_NOTIFY Windows message. In case not try to isolate when
> the memory leak appears and comment some parts of the code
> until it disappears.
> BTW, try to run the program with absolutely no break points
> an see if the memory leak persists.
>
> Regards, --
> Ignacio Ortiz de Zúñiga
> [Equipo de Xailer/Xailer team]
> http://www.xailer.com
> http://www.xailer.info