in reply to To each() their own

Your speculation that the warning comes from XS code sounds plausible.

I'd use the common debugging technique: reduce the code until you don't get the warning anymore. The last part removed is probably responsible for it, so return it back, and try to reduce the code elsewhere. In the end, you should have just several lines of code with a small number of dependencies. Then come back here and ask again, or answer your own question.

> however it has a serious memory leak in it

Sounds interesting. Can you give more details? How do you detect memory leaks?

($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord }map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

Replies are listed 'Best First'.
Re^2: To each() their own
by Ancient.Wizard (Novice) on May 02, 2017 at 12:01 UTC
    The memory leak is already well known to the Perl developers. Apparently the RE compiler and perhaps something in Encode which may just be the same RE issue eats memory like a hungry monster. The tickets on the subject all provide small code samples that will exploit the leak. My application will crap out in an hour or so. I'm on Linux and the application will be killed by the OS once it stresses the system for memory. At this time the RSS should be less than 500MB. The sample memory leak example looks something like this. You wont be able to run it because a helper module I'm using here is unavailable to you.
    $ perl -MSimple::HostStat -MEncode -e 'my $m=Simple::HostStat->new; wh +ile (1) { encode("ascii", substr("test",1)); if ( int(rand(350000)) = += 1 ){printf "# %s\n", $_ for ( $m->toConsole ) }}' # However I think the original (something like this) and a command lik +e top will also due fine $ perl -MEncode -e 'while (1) { encode("ascii", substr("test",1)) }'
      Thanks. The link to the ticket would've been enough.

      ($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord }map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,