ConcurrentModificationException in saved diagram index #1612
Comments
Several code reviews have been conducted. So far, the only plausible explanation so far is that SavedDiagramIndexInvalidator, a resource change listener, is being called while fetching information about the diagrams. Adjustments to the saved diagram index is protected by synchronized blocks but it appears that the invalidator is being called by the same thread. Although the issue hasn't been reliably reproduced, it has been confirmed that the change listeners will be notified in the running thread under certain circumstances. The theory is that while walking the workspace tree, Eclipse determined that something has changed and sends out notifications. |
philip-alldredge
added a commit
that referenced
this issue
Oct 24, 2018
philip-alldredge
added a commit
that referenced
this issue
Oct 24, 2018
@philip-alldredge Is this fixed with PR #1613? |
Yes. Closing... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A ConcurrentModificationException can occur when opening a diagram using the context menu.
The text was updated successfully, but these errors were encountered: