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

Make constantCases and variableCases in the GdlPool thread-safe #52

Closed
AlexLandau opened this issue Apr 19, 2014 · 2 comments
Closed

Make constantCases and variableCases in the GdlPool thread-safe #52

AlexLandau opened this issue Apr 19, 2014 · 2 comments
Assignees

Comments

@AlexLandau
Copy link
Member

Currently they are TreeMaps accessed without any concurrency protection. Luckily, they're turned off by default, except when used in the Server app.

@AlexLandau AlexLandau self-assigned this Apr 19, 2014
@AlexLandau
Copy link
Member Author

There are also concurrency issues around drainPool(), but those are unavoidable. (If someone calls it while there are references to Gdl objects other than the keyword constants floating around, bad things will happen.)

@AlexLandau
Copy link
Member Author

#54

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