According to perldiag, this message is considered a warning.
You shouldn't be dismissing the severity. The code is accessing a freed memory!
My current theory is that the free() call is failing even when I don't see any output. Is that assumption reasonable?
Accessing freed memory can lead to a wide variety of behaviour. It's a waste of time looking at this when you already know what leads to this memory corruption (accessing a freed scalar).
So far, I have not successfully isolated the problem.
An alternate approach would be to find the commit that fixed the problem. This might give a hint how to work around the problem in the versions before it was fixed.
There are tools to bisect history to find what a problem started occurring, or in this case, stopped occurring. I don't know how easy it would be to automatically install modules as part of the process.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||