Community
Participate
Working Groups
While debugging bug 566262 I've stumbled over this issue. org.eclipse.jdt.internal.core.search.indexing.IndexRequest.isCancelled is not volatile but it is accessed from multiple threads, not always inside synchronized blocks => the threads may see a stale, not up-to-date version of the object. I will push a patch.
New Gerrit change created: https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/171750
Gerrit change https://git.eclipse.org/r/c/jdt/eclipse.jdt.core/+/171750 was merged to [master]. Commit: http://git.eclipse.org/c/jdt/eclipse.jdt.core.git/commit/?id=2e32a2ed13ae0ec07169e093317dfa8b18d8f60f
verified by code inspection