Now we get to the nitpicking part. Just out of curiousity:

Is this something you might expect when using threads (global vars gone but function still active) or is this a (Pike) problem?

On 3/29/2010 14:50, Marcus Agehall (nu med K-märkt fastighet) @ Pike (-) developers forum wrote: 
What you need to do to avoid these errors, is to make sure your own
worker thread stops before you return from stop() in your module,
otherwise you have races that can break all sorts of things.


--
Signature Met vriendelijke groet / With kind regards / mit besten Grüßen,
Coen Schalkwijk
Software Engineer

coen.schalkwijk@rtl.nl

coen@rtlinteractief.nl

+31 (0)35 671 8915