In QNamePool::remove() there is this code:

// Tail call. Should avoid deadlock because no new stack frame.
normVictim->removeReference();

Even if this is not an out-right bug, i think it is dangerous to reply on 
tail-recursion optimization of the underlying compiler. 

I understand that the current trunk code has the same problem.  

Do you want to fix it, i.e. release the lock before calling 
normVictim->removeReference()?


-- 
https://code.launchpad.net/~zorba-coders/zorba/qname-pool-refactoring/+merge/94953
Your team Zorba Coders is subscribed to branch lp:zorba.

-- 
Mailing list: https://launchpad.net/~zorba-coders
Post to     : zorba-coders@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zorba-coders
More help   : https://help.launchpad.net/ListHelp

Reply via email to