Re: help with memory leak

Could you post a combination of parameters that causes problems? I guess $rep is sufficient.

Another idea would be to isolate your code from the Poly::Solve module. In the current code they are somehow linked through the @zeroes array, even though this should not be. If you do

$haystack{"$a, $b, $c"} =  join "|", @zeros;
[download]

as a test, this coupling should be much weaker as you only keep a string containing your results and not a reference.

Comment on Re: help with memory leak Download Code

Replies are listed 'Best First'.
Re^2: help with memory leak by crunch_this! (Acolyte) on Apr 16, 2013 at 21:21 UTC
Changing `\@zeros` to `join "\|", @zeros` fixes the leak on the line containing `my @zeros = poly_roots(@derivative);` but not the one with the hash definition. I have no idea why. Changing that also affects things later in the program, but right now I guess my priority is to fix this leak. & I added a line to the original message to explain what $rep is	[reply] [d/l] [select]
Re^3: help with memory leak by bioinformatics (Friar) on Apr 17, 2013 at 04:31 UTC
The "$a, $b, $c" portion of the hash uses scalars being passed in to the derivative function in @quartic. If you copy the loop counters like `my $a_copy = $a` and use those in @quartic, you may be able to bypass the scalar leak. I would say the module has some issues, but it looks like you can bypass them. Bioinformatics	[reply] [d/l]