Re: Memory leak with inout parameters

* Alex Hornby
> Are the leaks in the client or the server? 

Sorry, they're in the server.

> If you are on Linux you could try running your tests under valgrind (
> see http://developer.kde.org/~sewardj/ ).

Yes, I've tried that.  For a testcase where I lose 500K (1000K under
valgrind), valgrind reports

==12511== definitely lost: 112 bytes in 6 blocks.
==12511== possibly lost:   246 bytes in 5 blocks.
==12511== still reachable: 1582707 bytes in 22694 blocks.

The only block which seems to be large enough to include my leaks is

==12511== 1529740 bytes in 22314 blocks are still reachable in loss record 17 of 17
==12511==    at 0x400451CB: malloc (vg_clientfuncs.c:100)
==12511==    by 0x808B5CB: Perl_safemalloc (in /usr/bin/perl)
==12511==    by 0x809D385: (within /usr/bin/perl)
==12511==    by 0x80A1B3A: Perl_newSV (in /usr/bin/perl)

which seems to indicate that the leak is in Perl- or xs-space
somewhere.


							Arne.