There is an unsaved comment in progress. You will lose your changes if you continue. Are you sure you want to reopen the work item?
Not all of the awaiting reader locks informed when writer lock is released
In case we have a process holding write lock and few processes trying to acquire read lock (waiting for some timeout), only first one reader will be informed when writer lock will be released - it will acquire reader lock immediately and Group.ReadLock(string
lockName, int timeout) will return true. Other awaiting processes will keep waiting until the timeout is expired and return false then.
However, you can try to call ReadLock() once again then and it will acquire reader lock immediately.
I'm not 100% sure it's an issue, but looks like all of the awaiting readers should be granted with reader lock, not only the first one.
I'm also was unable to find exact Vsync version number in source code, so probably it's worth to add it.