You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a very subtle bug in TaskResultCache that is causing the same lock object to be used rather than a different one per key. Here's the offending code:
object lockObject = _perTaskLock.GetOrAdd(key, static () => new object());
This erroneously caches the delegate that is used. The intent was to pass in a delegate that will create a new object and cache/lock on that.
The text was updated successfully, but these errors were encountered:
There is a very subtle bug in
TaskResultCache
that is causing the same lock object to be used rather than a different one per key. Here's the offending code:object lockObject = _perTaskLock.GetOrAdd(key, static () => new object());
This erroneously caches the delegate that is used. The intent was to pass in a delegate that will create a new object and cache/lock on that.
The text was updated successfully, but these errors were encountered: