-
Notifications
You must be signed in to change notification settings - Fork 577
keys()/each() leak memory with threads::shared #10723
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
Comments
From @jdheddenCreated by @jdheddenUsing keys() and/or each() on threads::shared hashes causes a significant my $hash = &threads::shared::share({}); for (1..$MAX_LOOP) { The attached test script contains the above as well as some variants My suspicion is that the HvKEYS() call in the following code from /* Len magic for PERL_MAGIC_tied(P) */ U32 Perl Info
|
From @jkeenanOn Wed Oct 13 12:45:28 2010, jdhedden@cpan.org wrote:
Reviewing this older ticket tonight, I built a threaded perl (see attachment for perl -V) at HEAD of blead, then ran the test script which Jerry provided a couple of years back. This was the output: The program completed in 0m0.779s. Should I have expected to see some error output? Has the bug somehow been fixed? Thank you very much. -- |
From @jkeenan |
From @jkeenanSummary of my perl5 (revision 5 version 21 subversion 5) configuration: Characteristics of this binary (from libperl): |
The RT System itself - Status changed from 'new' to 'open' |
From @iabynOn Mon, Sep 22, 2014 at 06:50:03PM -0700, James E Keenan via RT wrote:
Increase $MAX_LOOP so that each loop runs for longer, then execute while However, it appears to have been fixed sometime between 5.16.0 and 5.18.0 -- |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#78362 (status was 'resolved')
Searchable as RT78362$
The text was updated successfully, but these errors were encountered: