Skip to content

Don't use Display.syncExec() for refresh in RuntimeClasspathViewer#681

Merged
iloveeclipse merged 1 commit intoeclipse-jdt:masterfrom
iloveeclipse:issue_672
May 1, 2025
Merged

Don't use Display.syncExec() for refresh in RuntimeClasspathViewer#681
iloveeclipse merged 1 commit intoeclipse-jdt:masterfrom
iloveeclipse:issue_672

Conversation

@iloveeclipse
Copy link
Copy Markdown
Member

The listener may be called from a background thread that already holds some locks. To refresh RuntimeClasspathViewer UI in the current case, syncExec is not needed, asyncExec is enough and it would not acquire the UI lock from an unknown thread.

Fixes #672

The listener may be called from a background thread that already holds
some locks. To refresh RuntimeClasspathViewer UI in the current case,
syncExec is not needed, asyncExec is enough and it would not acquire the
UI lock from an unknown thread.

Fixes eclipse-jdt#672
@iloveeclipse
Copy link
Copy Markdown
Member Author

Thanks @basilevs, I've updated patch.

@iloveeclipse iloveeclipse merged commit 2e1facd into eclipse-jdt:master May 1, 2025
11 checks passed
@iloveeclipse iloveeclipse deleted the issue_672 branch May 1, 2025 11:55
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

Successfully merging this pull request may close these issues.

Deadlock in ExecutionEnvironmentsPreferencePage

2 participants