Bug 578789 - Deadlock situation when adding new JRE

Don't use syncExec() for tasks that can be done asynchronously. The
listener can be called from the thread that holds already a lock.

Change-Id: Ic2029ae0e395a31564c97e6233ce6596086dd7f6
Reviewed-on: https://git.eclipse.org/r/c/jdt/eclipse.jdt.debug/+/190854
Tested-by: JDT Bot <jdt-bot@eclipse.org>
Reviewed-by: Andrey Loskutov <loskutov@gmx.de>
diff --git a/org.eclipse.jdt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/jres/InstalledJREsBlock.java b/org.eclipse.jdt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/jres/InstalledJREsBlock.java
index 1911a08..59852dc 100644
--- a/org.eclipse.jdt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/jres/InstalledJREsBlock.java
+++ b/org.eclipse.jdt.debug.ui/ui/org/eclipse/jdt/internal/debug/ui/jres/InstalledJREsBlock.java
@@ -153,7 +153,7 @@
 				fVMList.refresh();
 			}
 			else {
-				display.syncExec(new Runnable() {
+				display.asyncExec(new Runnable() {
 					@Override
 					public void run() {
 						fVMList.refresh();