Jeremy Hylton wrote: > > We've also seen this error in some internal projects here, but aren't > any closer to figuring out the cause than you are :-(. Any hints on hunting this kindof thing, or anywhere else where _my_ code may be leaking memory, would be very gratefully recieved :-S cheers, Chris