New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recursion memory leak when assignment in if condition #9426
Comments
From Thushan.Abeysekera@computershare.comCategory: core Severity: medium Originally observed in: perl, v5.8.6 built for MSWin32-x86-multi-thread This problem can be replicated in perl 5.10.0 i686-linux-thread-multi. Please check http://www.perlmonks.org/?node_id=698735 for a discussion Thanks, Thushan Abeysekera Programmer Analyst Computershare ****************************************************************************** ****************************************************************************** |
From Thushan.Abeysekera@computershare.comCreated by thushan.abeysekera@computershare.comThis is a bug report for perl from thushan.abeysekera@computershare.com, ----------------------------------------------------------------- Script 1 (This has the memory leak):use strict; sub test1 { sub get_true { Script 2 (This runs without a problem):use strict; sub test1 { sub get_true { Originally observed in: perl, v5.8.6 built for MSWin32-x86-multi-thread This problem can be replicated in perl 5.10.0 i686-linux-thread-multi. Please check http://www.perlmonks.org/?node_id=698735 for a discussion on this. Perl Info
|
From p5p@perl.wizbit.beCiteren Thushan Abeysekera <perlbug-followup@perl.org>:
[snip]
$ cat rt-57174.pl use strict; my my $m = 0; my if ($vsz1 + 1000 < $vsz2) { sub test1 { sub get_true { __END__ (running with user 'perl') perl-5.00504 rt-57174.pl perl-5.10.0 rt-57174.pl perl-blead@34156 rt-57174.pl (No access to a system with a perl before 5.00504 atm) Kind regards, Bram |
The RT System itself - Status changed from 'new' to 'open' |
From @iabynLeak still present in bleed@35059, Dec 2008. |
Migrated from rt.perl.org#57174 (status was 'open')
Searchable as RT57174$
The text was updated successfully, but these errors were encountered: