An extensive evaluation of how redundant synchronization object calls behaved and interacted with our internal thread impersonation logic was examined. A redundant synchronization call is a call by a thread that succeeds without actually attempting to acquire the synchronization object because the object is already held by the thread. Most importantly, only one call will be made to release the object. Although c-treeACE does not use recursive mutex/semaphore calls, it may allow a mutex/semaphore to be called by the same thread that already owns the synchronization object. We addressed a number of internal details in this area resulting in an overall improvement.