> OK, so on the spamd hang bugs, we have:
>
> - a set of people reporting hangs predominantly (all?) when running spamd
> on hyperthreaded CPUs
> - not all HT CPUs are acting up
> - a hang traced into Storable::dclone() (thanks Dallas!)
>
> so I think we may have run into a perl thread-safety bug, possibly
> in Storable, possibly at a lower level, and running on HT cpus causes
> this bug to manifest itself.
>
> Another reason to get rid of our use of Storable, in my opinion.
>
> --j.
The ChangeLog for Storable-2.13 has:
Version 2.10
1. Thread safety: Storable::CLONE/init_perlinterp() now create
a new Perl context for each new ithread.
(From Stas Bekman and Jan Dubois.)
2. Fix a tag count mismatch with $Storable::Deparse that caused
all back-references after a stored sub to be off-by-N (where
N was the number of code references in between).
(From Sam Vilain.)
3. Prevent CODE references from turning into SCALAR references.
(From Slaven Rezic.)
As Dallas is running Storable-2.08, it might be worthwhile to try the
latest version. That is not to say that getting rid of Storable is
not a good idea.
Tom schulz
Applied Dynamics Intl.
[EMAIL PROTECTED]
