Hm. I cannot even begin to imagine the circumstances that would allow that (duplicate hash keys) to happen. More importantly, how it could possibly get past regression testing into the wild. No matter. The versions you are using are well down level, and anyone can make a mistake.
Upgrade! Get the latest cpan versions of both threads and threads::shared--1.71/1.27--respectively. If you can reproduce the results once you've done that, you need to raise a perlbug immediately. Hopefully this is just the result of an unfortunate mix of intermediate releases.
In reply to Re^15: does threads (still) memleak?
by BrowserUk
in thread does threads (still) memleak?
by faxm0dem
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |