-
Notifications
You must be signed in to change notification settings - Fork 115
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Asset.cs not thread safe #101
Comments
I am seeing this happen in my production site as well |
same here :( |
I'm getting the same error Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct
Maybe change this Items to a ConcurrentDictionary would work? / m |
is there any update on this file? we have seen this issue twice this week, we have updated it from 3.0.250 to 3.0.311 but the issue is still there and we found it in this file. do we have a plan? also, there seems a breaking change thus we can't directly update to the latest version with no code change. |
Asset.GenerateCacheKey is modifying a standard (non-thread safe) Dictionary and doesn't appear to be protected by a thread mutex/lock. If multiple requests/threads attempt to access the same resource immediately after startup, it results in the Items dictionary becoming corrupt.
Ex:
The text was updated successfully, but these errors were encountered: