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

fatal error: concurrent map writes #44

Open
Brett-Kavanaugh opened this issue Oct 13, 2018 · 1 comment
Open

fatal error: concurrent map writes #44

Brett-Kavanaugh opened this issue Oct 13, 2018 · 1 comment

Comments

@Brett-Kavanaugh
Copy link

Hello,

I get the above panic when I try and mark two things dirty at nearly the same time. I can fix the above myself by changing my program but I think it would be good for you to implement a locking system if at all possible to prevent this.

Thank you!

@icza
Copy link
Owner

icza commented Oct 14, 2018

There is locking implemented already, which should prevent concurrent modification. The current locking is done at session level. Note that "sessionless" clients also have a shared, public session, so if you only access gowut components and session objects from event handlers, the error you get should never occur.

Please post your code that reproduces the error you experience.

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

2 participants