| # | Subject | Status | Queue | Owner | Priority |
|---|---|---|---|---|---|
| Requestors | Created | Told | Last Updated | Time Left | |
| 134305 | Memory Leak in perl 5.28 and 5.30 | open | perl5 | Nobody | 0 |
| a.shikov@dtel-ix.net | 5 years ago | 5 years ago | 5 years ago | ||
| 130270 | fuzzing testcase triggers LeakSanitizer over 101 byte memory leak | open | perl5 | Nobody | 0 |
| brian.carpenter@gmail.com | 7 years ago | 5 years ago | 5 years ago | ||
| 133589 | regex compilation can leak memory | open | perl5 | Nobody | 0 |
| public@khwilliamson.com | 6 years ago | 5 years ago | 5 years ago | ||
| 132892 | Possibly memory leak when matching strings using pre-compiled regexes stored in hash key (perl >= v5.26) | open | perl5 | Nobody | 0 |
| rootkwok@cpan.org | 6 years ago | 6 years ago | 6 years ago | ||
| 130494 | [CONC] [PERF] Using Proc::Async with tap leads to memory leak | open | perl6 | jnthn@jnthn.net | 0 |
| ronaldxs@software-path.com | 7 years ago | 6 years ago | 6 years ago | ||
| 132104 | [JVM] EvalServer leaks threads and memory when using Proc::Async | open | perl6 | Nobody | 0 |
| alex.jakimenko@gmail.com | 7 years ago | 6 years ago | 6 years ago | ||
| 131829 | Weird memory leakage of sequences and other things ( (1…∞).grep(* < 0)[^10] ) | open | perl6 | Nobody | 0 |
| alex.jakimenko@gmail.com | 7 years ago | 7 years ago | 7 years ago | ||
| 131643 | Memory leak in Perl_re_op_compile | new | perl5 | Nobody | 0 |
| sergey.aleynikov@gmail.com | 7 years ago | 7 years ago | |||
| 131636 | Memory leak in Perl_yylex | new | perl5 | Nobody | 0 |
| sergey.aleynikov@gmail.com | 7 years ago | 7 years ago | |||
| 127632 | regex compilation leaks memory when warnings are made FATAL | open | perl5 | Nobody | 0 |
| khw@cpan.org | 8 years ago | 7 years ago | 7 years ago | ||
| 126189 | [PERF] `loop { 0, .1 ... 1000 }` leaks memory | open | perl6 | Nobody | 0 |
| larry@wall.org | 9 years ago | 7 years ago | 7 years ago | ||
| 57174 | Recursion memory leak when assignment in if condition | open | perl5 | Nobody | 0 |
| Thushan.Abeysekera@computershare.com | 16 years ago | 16 years ago | 8 years ago | ||
| 128209 | Failed XSLoader::load() leaks memory | open | perl5 | Nobody | 0 |
| 8 years ago | 8 years ago | ||||
| 127657 | There are a bunch of memory leaks when doing 'make test' | open | perl5 | Nobody | 0 |
| khw@cpan.org | 8 years ago | 8 years ago | 8 years ago | ||
| 118815 | Memory leak when thread terminated abnormally | open | perl5 | Nobody | 0 |
| haze@arpstorm.net | 11 years ago | 11 years ago | 11 years ago | ||
| 22121 | memory leaking in perl_destruct and perl_free ? | open | perl5 | Nobody | 0 |
| Haili.Ma@netiq.com | 21 years ago | 12 years ago | 12 years ago | ||
| 44253 | Memory leak in tied Hash | open | perl5 | Nobody | 0 |
| holger.seelig@yahoo.de | 17 years ago | 17 years ago | 16 years ago |
This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.
For issues related to this RT instance (aka "perlbug"), please contact perlbug-admin at perl.org