Skip to content
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

Operations that change non-concurrent collections must have exclusive access #45

Open
richard-churchman opened this issue Jun 22, 2024 · 0 comments

Comments

@richard-churchman
Copy link
Contributor

2024-06-22 21:13:15,819 Entity Invoke: GUID a7e70157-0002-45d0-8ac3-92d4e65e539c and model 1 has created a general error as System.InvalidOperationException: 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.
at System.Collections.Generic.Dictionary2.TryInsert(TKey key, TValue value, InsertionBehavior behavior) at System.Collections.Generic.Dictionary2.Add(TKey key, TValue value)
at Jube.Engine.Invoke.EntityAnalysisModelInvoke.WaitReadTasks(List`1 pendingReadTasks) in /home/richard.churchman/RiderProjects/jube/Jube.Engine/Invoke/EntityAnalysisModelInvoke.cs:line 826
at Jube.Engine.Invoke.EntityAnalysisModelInvoke.Start() in /home/richard.churchman/RiderProjects/jube/Jube.Engine/Invoke/EntityAnalysisModelInvoke.cs:line 748.

This has been an error that has long since needed attention and relates to counter functionality use of collections for these counter. More generally the int's should be of a safe type for multi threading and the collections used should be concurrent. I would prefer to not Sync Lock around bits of code if there is already a tool available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant