Fix of CME in MyJavaFileManager.list #104
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
MyJavaFileManager#list
is synchonized, butJavacFileManager#pathsAndContainersByLocationAndRelativeDirectory
can be modified by another thread when executingMyJavaFileManager#handleOption
.Thread that throws CME:
Concurrent thread:
This is obviously not a proper fundamental solution: we still have concurrent access to HashMap inside file manager. But from a practical standpoint, this fix decreases change of CME (when compiling 10+ method readers in parallel) from ~5% to "can't reproduce".