-
Notifications
You must be signed in to change notification settings - Fork 561
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
Memory leak with anonymous sub scoped outside another anonymous sub #22893
Labels
Comments
Based on vibes, this may be a duplicate of #22547. |
I modified the OP's program, mostly to add debugging statements:
I then used this program to bisect with this invocation:
More than 4 hours later, I got this result:
@tonycoz, can you take a look? Thanks. |
Should be fixed by 9059509 |
Confirmed.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Cc: builduser
To: [email protected]
Message-Id: 5.40.0_37134_1736241991@ARCH
Subject: Memory leak with anonymous sub scoped outside another anonymous sub
From: [email protected]
Reply-To: [email protected]
This is a bug report for perl from [email protected],
generated with the help of perlbug 1.43 running under perl 5.40.0.
Description
There is a memory leak (illustrated in the code below), which can be reproduced with
perl-5.40.0
andperl-5.41.7
, but CANNOT be reproduced with old enough versions of Perl.Running under perl-5.40.0, the code below, ends up using more than 1GB of RAM:
Running under perl-5.22.3, RAM usage stays stable at ~100MB:
Steps to Reproduce
Expected behavior
The
$block
and$t
variables should be destroyed after each loop iteration.Flags
Perl configuration
The text was updated successfully, but these errors were encountered: