Roger, your explanation might have hit the bug behind it. (I don't comment, as it is speculation any way. We all know that they fixed lots of thread-related memory leaks in 5.8.2, at least according to the document. It is not a surprise that they might had some of the bugs over killed, and now free the same piece allocated memory twice. Not neccessary to be garbage collector related ;-)
However this is not a fix, but rather a workaround, as the OP's code should be just fine, without the array you added. A Perl bug is still a Perl bug, and there is no point for application programmer to suffer from it, and worry about workaround.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.