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
thread constructor with arguments can leak #9969
Comments
From @ikegamiCreated by @ikegamiThe following code has Perl saying "Scalars leaked: 1" numerous times. ----BEGIN CODE---- use threads; sub PINGIT { sub THPING { { ----BEGIN OUTPUT---- The leak goes away if no additional arguments are passed to ->create. The Perl Info
|
From @jdhedden
This is another example of a known 'threads' problem involving leaked Dave Mitchell is has looked at this issue, but does not have a fix. This bug report and bug reports 41138, 41816 and 66108 (and possibly |
The RT System itself - Status changed from 'new' to 'open' |
From @dkCreated by @dkThe code below produces warning "Scalars leaked: 1". It does so on use threads; sub moo moo($X); Perl Info
|
From @obra
And it does on Debian's 5.8.8 (Linux x86) as well. |
The RT System itself - Status changed from 'new' to 'open' |
From @ikegamiOn Tue, Dec 1, 2009 at 10:29 AM, Dmitry Karasik
It's a case of a known problem. The workaround is to add @_=(); in moo().
sub moo moo($X);
This is the same problem as the one reported in |
@iabyn - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#70602 (status was 'resolved')
Searchable as RT70602$
The text was updated successfully, but these errors were encountered: