I do not believe this is because of anything explicit in the C routines since there is only one malloc call, ... and such a leak would grow in a regular linear fashion every time a new memory page was needed.
That is a bad assumption. Perl's memory allocator often requests a power-of-two sized large chunk of memory from the OS which it then parcels out to the program as a bunch of smaller requests on demand.
My guess is that you are failing to mortalise the SV which you are populating with the inbound data.
If you posted the code, it would probably be the work of a few minutes to confirm that or otherwise track the leak down.
In reply to Re: Tracing memory leak
by BrowserUk
in thread Tracing memory leak
by halfcountplus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |