Troubleshooting Eclipse exception Shutdown After restarting the org.eclipse.swt.SWTException:Invalid thread access

.

.

.

.

.

A long time did not write a blog, is really too busy recently, always wanted to write something dry, but has not been quiet to learn.

Today, working overtime, who knows the busier the more problems. First WebLogic No normal start, by experience the first reaction is the 7001 port is occupied by other programs, and then through the command to view, found that it is occupied, occupy the port is eclipse, find the way to occupy the port, please move to the blogger's another article "Windows" Query the program that occupies the port--remember to resolve the process of WEBLOIGC startup failure.

Prior to eclipse, which did not occupy Port 7011, the occupancy estimate might have been to launch a random port that happened to occupy the WebLogic Web service port. Now that you have found the culprit, restart Eclipse. Who knows when clicking the Close button, there is no popup confirmation exit dialog box, but the interface disappears directly, but the process has not disappeared. Intuition tells bloggers: "Broken, may have a problem." As expected, again start will pop up a hint that you have encountered a problem, see Workspace/.metadata/.log file for details. Bloggers Open this log file to see, the inside reported an exception:

Org.eclipse.swt.SWTException:Invalid Thread Access

At Org.eclipse.swt.SWT.error (swt.java:4397)
At Org.eclipse.swt.SWT.error (swt.java:4312)
At Org.eclipse.swt.SWT.error (swt.java:4283)
At Org.eclipse.swt.widgets.Display.error (display.java:1258)
At Org.eclipse.swt.widgets.Display.checkDevice (display.java:764)
At Org.eclipse.swt.widgets.Display.addListener (display.java:626)
At Org.eclipse.ui.internal.ide.application.ideworkbenchadvisor.<init> (ideworkbenchadvisor.java:176)
At Org.eclipse.ui.internal.ide.application.ideworkbenchadvisor.<init> (ideworkbenchadvisor.java:184)
At Org.eclipse.ui.internal.ide.application.IDEApplication.start (ideapplication.java:125)
At Org.eclipse.equinox.internal.app.EclipseAppHandle.run (eclipseapphandle.java:196)
At Org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication (eclipseapplauncher.java:110)
At Org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start (eclipseapplauncher.java:79)
At Org.eclipse.core.runtime.adaptor.EclipseStarter.run (eclipsestarter.java:354)
At Org.eclipse.core.runtime.adaptor.EclipseStarter.run (eclipsestarter.java:181)
At Sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
At Sun.reflect.NativeMethodAccessorImpl.invoke (nativemethodaccessorimpl.java:39)
At Sun.reflect.DelegatingMethodAccessorImpl.invoke (delegatingmethodaccessorimpl.java:25)
At Java.lang.reflect.Method.invoke (method.java:597)
At Org.eclipse.equinox.launcher.Main.invokeFramework (main.java:636)
At Org.eclipse.equinox.launcher.Main.basicRun (main.java:591)
At Org.eclipse.equinox.launcher.Main.run (main.java:1450)

The general meaning of this exception is that it is not allowed to manipulate UI components in non-SWT threads, otherwise this exception will be thrown.

Well, a stack of information is not like a plug-in caused by a bug in Eclipse 4.3? Let's not dig into it.

Let's talk about how this problem is solved.

Toss for a long time, Bo master almost re-installed system, and later found that the solution is very simple, only need to add a-clean parameter when Eclipse first start , the next time you start without adding this parameter.

To explain briefly what this parameter does, eclipse caches the plug-in in order to speed up the startup, but it happens that these caches sometimes have problems, so let Eclipse erase the cache with the-clean parameter, but after adding this parameter, eclipse The boot speed will be slower, fortunately only one use.