[sldev] Memory leaks/leftover almost completed

[Max Okumoto]

If you are building on Linux and using valgrind Bryan O'Sullivan 
mentioned that
the tcmalloc() libraries and valgrind are in compatible.  So you will 
need to link
without tcmalloc to use valgrind.

          Max


Nicholaz Beresford wrote:
>
> Callum Lerwick wrote:
>> On Tue, 2007-06-19 at 14:10 +0200, Nicholaz Beresford wrote:
>>> http://nicholaz-beresford.blogspot.com/2007/06/memory-leaksleftover-almost-completed.html 
>>>
>>
>> Just wondering, what OS, compiler and debug tool are you using for your
>> leak debugging? Windows, right?
>>
>> I've been toying with running the client (Linux/gcc) under valgrind, and
>> there appears to still be plenty to clean up. 
>
> Yes, I'm running under Windows with the Microsoft debug malloc
> routines ... it's just a small patch to the code and then running
> the debug version under VS2003 does it.
>
> It's still slow as molass, so nothing to do and enjoy an SL session
> and check the log afterwards, but good enough for dedicated leak
> hunting.
>
> Downside is currently that (as Able observed recently) that under
> VS2005 it doesn't compile as a debug version because one of the
> libs (libmoz) interferes, so it's probably useful for as many
> people as it could.
>
> But from my tests (leak dump and memory usage under normal conditions),
> under Windows the whole thing is pretty much under control.
>
> I'm aware of one area which needs attention.  It's not exactly
> leaking, but progressively growing until it's all cleaned up at
> the end, but besides that, real leaks are down to minimal (with
> the stuff I have tested and observed).
>
>
> Nick
> _______________________________________________
> Click here to unsubscribe or manage your list subscription:
> /index.html