-
Notifications
You must be signed in to change notification settings - Fork 556
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 in regex appears in 5.20.1 #14236
Comments
From arocker@vex.netA memory leak from a previously-working regex has been posted in This is obviously not a satisfactory report, but if a maintainer contacts |
From @iabynOn Thu, Nov 13, 2014 at 06:30:47AM -0800, arocker@vex.net wrote:
Yes, please supply some more info -- |
The RT System itself - Status changed from 'new' to 'open' |
From arocker@vex.net---------------------------- Original Message ---------------------------- The poster in LinkedIn's "Perl" discussion group is Nimrod Shlomo Chotzen Initial message: I switched this week to using perl-5.20.1, and I try to run an old (but foreach my $key_word (grep {/\w+/} @keywords) { } the memory usage increases very fast. at the next call of that function it Second: I simplified the regexp to this: Response to a request for sample data: there are no two different datasets. just different perls 5.18.2 and something like: "lantern,green lantern,green lantern It looks like a failure to free memory in the handling of regex patterns. |
From @iabynOn Fri, Nov 14, 2014 at 09:38:38AM -0500, arocker@Vex.Net wrote:
I've managed to reproduce it with the following self-contained script: my @keywords; foreach my $key_word (grep {/\w+/} @keywords) { } and bisected it using this (the perl binary is passed as a command-line $x = `/usr/bin/time -v $ARGV[0] /home/davem/tmp/p 2>&1`; $x =~ /Maximum resident set size \(kbytes\): (\d+)/ It bisects to the following. I haven't looked further yet. Karl, is this commit 3c075fe PATCH [perl #121144]: \S, \W, etc fail for above ASCII -- |
From @khwilliamsonOn 11/17/2014 05:14 AM, Dave Mitchell wrote:
Not particularly, but I'm doing it anyway |
From @khwilliamsonOn 11/17/2014 05:14 AM, Dave Mitchell wrote:
A fix is now smoking in http://perl5.git.perl.org/perl.git/shortlog/refs/heads/smoke-me/khw-leak This passes your test, but I tried getting blead to fail with the (For future readers trying to reproduce this, the file in the script |
From @cpansproutOn Mon Nov 17 21:26:52 2014, public@khwilliamson.com wrote:
I have just added a to-do test in commit 43275f0. -- Father Chrysostomos |
From @khwilliamsonNow fixed by commit 512e01a Thanks for the help in tracking this down and making a test for it. This should be a candidate for the next 5.20 maint release -- |
@khwilliamson - Status changed from 'open' to 'resolved' |
From @khwilliamsonReopen so can be moved to pending release, instead of resolved |
@khwilliamson - Status changed from 'resolved' to 'open' |
@khwilliamson - Status changed from 'open' to 'pending release' |
From @cpansproutOn Tue Nov 18 09:13:53 2014, khw wrote:
It gets my wote. -- Father Chrysostomos |
From @khwilliamsonThanks for submitting this ticket The issue should be resolved with the release today of Perl v5.22, available at http://www.perl.org/get.html -- |
@khwilliamson - Status changed from 'pending release' to 'resolved' |
Migrated from rt.perl.org#123198 (status was 'resolved')
Searchable as RT123198$
The text was updated successfully, but these errors were encountered: