gowut
gowut copied to clipboard
fatal error: concurrent map writes
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!
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.