in reply to Yet another Embedding question

A simple search for perl_free yields http://archive.develooper.com/perl5-porters@perl.org/msg97324.html, so it appears this may be a known issue. I once read on p5p (IIRC) that you shouldn't call perl_free more than once. I also found MemLeak in Perl from C Calls. I suggest you turn to perl5-porters, and hopefully one of the knowledgables will give you a more definitive answer (although given how much code you hide, that may not be entirely possible).

update: http://www.xray.mpe.mpg.de/cgi-bin/w3glimpse/perl5-porters?query=perl_free&errors=0&case=on&maxfiles=100&maxlines=30

BTW, calling this Yet another Embedding question doesn't improve searchability (retitle).

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

Replies are listed 'Best First'.
Re: Re: Yet another Embedding question
by tomw1975 (Sexton) on Jul 28, 2003 at 18:34 UTC
    Thanks - looks like an internal Perl issue... which is bad... I hope the Wise Ones know of a way to resolve this issue - else I will have to scrap the whole thing and re-write it in another language... Is that Blasphamy in here?
    my thanks to all that have attempted to look at this issue.
    Tom
[reply]
      A solution has been found!

      I moved the compilation of the perl script  perl_parse out of the loop and passed the pointer to the memory around in C - this cut the memory loss from 1072 down to 8 per message. Much more manageable!

      Thanks all
[reply]
[d/l]

In Section Seekers of Perl Wisdom