> From: Jeremy Nuss [mailto:[EMAIL PROTECTED]]
> I've gone through all my code a dozen time to ensure that there
> is no possibility that the offending Handles could be locked...
> and there isn't. They just plain get unlocked every time
Consider adding liberal amounts of assert code to help fin
You might want to try something like Jeff Ishaq's memory leak detecting
code. I don't remember if Jeff's code wraps MemHandleLock/Unlock, but it's
easy enough to add if it doesn't. For your particular problem, you could
probably get away with just wrapping MemHandleLock/Unlock. If you rely on
Mem[
