When using eclipse, the following problems occur: org. Eclipse. SWT. swterror: No more handles Solution

Source: Internet
Author: User

The following problems occur when using Eclipse:

! Entry org. Eclipse. osgi 4 0 15:49:55. 671
! Message application error
! Stack 1
Org. Eclipse. SWT. swterror: No more handles
At org. Eclipse. SWT. SWT. Error (SWT. Java: 3803)
At org. Eclipse. SWT. Graphics. image. INIT (image. Java: 1582)
At org. Eclipse. SWT. Graphics. image. <init> (image. Java: 177)
At org. Eclipse. SWT. Widgets. Composite. wm_paint (Composite. Java: 1367)
At org. Eclipse. SWT. Widgets. Control. windowproc (control. Java: 3842)
At org. Eclipse. SWT. Widgets. Canvas. windowproc (canvas. Java: 337)
At org. Eclipse. SWT. Widgets. display. windowproc (display. Java: 4541)
At org. Eclipse. SWT. Internal. win32. OS. updatewindow (native method)
At org. Eclipse. SWT. Widgets. decorations. setvisible (decorations. Java: 1389)
At org. Eclipse. SWT. Widgets. Shell. setvisible (shell. Java: 1764)
At org. Eclipse. SWT. Widgets. Shell. Open (shell. Java: 1150)
At org. Eclipse. jface. Window. Window. Open (window. Java: 797)
At org. Eclipse. UI. Internal. workbenchwindow. Open (workbenchwindow. Java: 778)
At org. Eclipse. UI. Internal. workbench $61. runwithexception (workbench. Java: 3402)
At org. Eclipse. UI. Internal. startupthreading $ startuprunnable. Run (startupthreading. Java: 31)
At org. Eclipse. SWT. Widgets. runnablelock. Run (runnablelock. Java: 35)
At org. Eclipse. SWT. Widgets. synchronizer. runasyncmessages (synchronizer. Java: 133)
At org. Eclipse. SWT. Widgets. display. runasyncmessages (display. Java: 3800)
At org. Eclipse. SWT. Widgets. display. readanddispatch (display. Java: 3425)
At org. Eclipse. UI. application. workbenchadvisor. openwindows (workbenchadvisor. Java: 803)
At org. Eclipse. UI. Internal. workbench $27. runwithexception (workbench. Java: 1363)
At org. Eclipse. UI. Internal. startupthreading $ startuprunnable. Run (startupthreading. Java: 31)
At org. Eclipse. SWT. Widgets. runnablelock. Run (runnablelock. Java: 35)
At org. Eclipse. SWT. Widgets. synchronizer. runasyncmessages (synchronizer. Java: 133)
At org. Eclipse. SWT. Widgets. display. runasyncmessages (display. Java: 3800)
At org. Eclipse. SWT. Widgets. display. readanddispatch (display. Java: 3425)
At org. Eclipse. UI. Internal. workbench. runui (workbench. Java: 2295)
At org. Eclipse. UI. Internal. workbench. Access $4 (workbench. Java: 2200)
At org. Eclipse. UI. Internal. workbench $ 5.run( workbench. Java: 495)
At org. Eclipse. Core. databinding. observable. realm. runwithdefault (realm. Java: 288)
At org. Eclipse. UI. Internal. workbench. createandrunworkbench (workbench. Java: 490)
At org. Eclipse. UI. platformui. createandrunworkbench (platformui. Java: 149)
At org. Eclipse. UI. Internal. Ide. application. ideapplication. Start (ideapplication. Java: 113)
At org. Eclipse. Equinox. Internal. App. eclipseapphandle. Run (eclipseapphandle. Java: 193)
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: 386)
At org. Eclipse. Core. runtime. adaptor. eclipsestarter. Run (eclipsestarter. Java: 179)
At sun. Reflect. nativemethodaccessorimpl. invoke0 (native method)
At sun. Reflect. nativemethodaccessorimpl. Invoke (unknown source)
At sun. Reflect. delegatingmethodaccessorimpl. Invoke (unknown source)
At java. Lang. Reflect. method. Invoke (unknown source)
At org. Eclipse. Equinox. launcher. Main. invokeframework (main. Java: 549)
At org. Eclipse. Equinox. launcher. Main. basicrun (main. Java: 504)
At org. Eclipse. Equinox. launcher. Main. Run (main. Java: 1236)

Solution:

Find the workbench. xml file under Eclipse/workspace/. Metadata/. plugins/org. Eclipse. UI. workbench in the directory and delete the file on the XML node.
<Mrulist>
</Mrulist>

And then run eclipse to test whether the problem has been solved.

If the problem persists, go to workbench. in the XML file, find the name of the program that was last run (that is, before an error). For example, I am running XXXXX. an SQL problem occurs.
XXXXX. SQL string, delete all relevant parts, and continue running.
You can.

Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.