Eclipse 错误:未处理的事件循环异常没有更多句柄
声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow
原文地址: http://stackoverflow.com/questions/15594590/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Eclipse Bug: Unhandled event loop exception No more handles
提问by HEADLESS_0NE
I've built a GUI using Swing and the MigLayout.
我已经使用 Swing 和 MigLayout 构建了一个 GUI。
I am using Eclipse 4.2.2 (64-bit) on Windows 7 Ultimate. Every time I click back into the window to edit my code, a popup comes up, then I'm prompted to restart Eclipse, and the Event log says the following:
我在 Windows 7 Ultimate 上使用 Eclipse 4.2.2(64 位)。每次我单击返回窗口以编辑我的代码时,都会出现一个弹出窗口,然后提示我重新启动 Eclipse,并且事件日志显示以下内容:
org.eclipse.swt.SWTError: No more handles
at org.eclipse.swt.SWT.error(SWT.java:4387)
at org.eclipse.swt.SWT.error(SWT.java:4276)
at org.eclipse.swt.SWT.error(SWT.java:4247)
at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
at org.eclipse.swt.widgets.Control.createHandle(Control.java:704)
at org.eclipse.swt.widgets.Label.createHandle(Label.java:199)
at org.eclipse.swt.widgets.Control.createWidget(Control.java:744)
at org.eclipse.swt.widgets.Control.<init>(Control.java:112)
at org.eclipse.swt.widgets.Label.<init>(Label.java:101)
...
I'm attaching screenshots of the error messages. Has anyone else encountered this bug with Eclipse? Do you know of a work-around or a fix?
我附上了错误消息的屏幕截图。有没有其他人在 Eclipse 中遇到过这个错误?您知道解决方法或修复方法吗?
采纳答案by Nineroad
There is a workaround: Change the Java editor to WindowBuilder.
有一个解决方法:将 Java 编辑器更改为 WindowBuilder。
Eclipse → Windows → Preferences → File Associations →, choose WindowBuilder Editoras Java default editor.
Eclipse → Windows → Preferences → File Associations →,选择WindowBuilder Editor作为 Java 默认编辑器。
回答by Brandon
I had the same problem, turned out that TeamViewer was causing this.
我遇到了同样的问题,结果是 TeamViewer 导致了这个问题。
In your TeamViewer go to:
在您的 TeamViewer 中转到:
Extras → Options → Advanced → QuickConnectbutton, configure it and disable the show QuickConnectbutton.
附加 → 选项 → 高级 → QuickConnect按钮,对其进行配置并禁用显示QuickConnect按钮。
回答by Rudi
As suggested by NineroadInstalling WindowBuilder as the default editor for files with a *.java extention fixed this issue for me.
正如Nineroad所建议的,将WindowBuilder安装为具有 *.java 扩展名的文件的默认编辑器为我解决了这个问题。
In Eclipse, navigate to Help > Install New Software
在 Eclipse 中,导航到帮助 > 安装新软件
Add http://archive.eclipse.org/windowbuilder/WB/release/R201309271200/4.3to the "Work with" path, select all components suggested, and install WindowBuilder.
将http://archive.eclipse.org/windowbuilder/WB/release/R201309271200/4.3添加到“Work with”路径,选择所有建议的组件,然后安装 WindowBuilder。
Once complete, Eclipse will request restart. Once restarted, within Eclipse navigate to Window > Preferences. In The Preferences dialogue-box navigate to General > Editor > File Associations. Under "File Associations" list, be sure to select *.javafile types. The bottom window (labeled "Associated Editors") should have WindowBuilderas an option. Select WindowBuilder and click "Default" to the right, to set WindowBuilder as your default *.java file editor.
完成后,Eclipse 将请求重新启动。重新启动后,在 Eclipse 中导航到Window > Preferences。在首选项对话框中导航到General > Editor > File Associations。在“文件关联”列表下,一定要选择*.java文件类型。底部窗口(标记为“Associated Editors”)应该有WindowBuilder作为一个选项。选择 WindowBuilder 并单击右侧的“默认”,将 WindowBuilder 设置为默认的 *.java 文件编辑器。
This fixed the SWT errorfor me.
这为我修复了SWT 错误。
Note: Eclipse Version: Kepler Service Release 2 Windows 7 64-bit
注意:Eclipse 版本:Kepler Service Release 2 Windows 7 64 位
回答by MattSidor
I had DisplayFusion running, which is a special Windows program used to manage multiple monitors. Turning it off seemed to fix this issue for me.
我运行了 DisplayFusion,这是一个用于管理多台显示器的特殊 Windows 程序。关闭它似乎为我解决了这个问题。
回答by Farewell
It is hardware problem at all.
根本就是硬件问题。
If you have nView, turn off Desktop Manager. In case of ATI, turn off HydraVision.
如果您有 nView,请关闭桌面管理器。如果是 ATI,请关闭 HydraVision。
This works fine on Eclipse Kepler (Standard) and Android Developer Tools Edition.
这在 Eclipse Kepler (Standard) 和 Android Developer Tools Edition 上运行良好。
回答by Andreas Dietrich
in short: check out if the bold sections below may save your day :-)
简而言之:看看下面的粗体部分是否可以挽救您的一天:-)
(This answer may help but the source problem is still not found. I'll update my findings if satisfyingly solved.)
(这个答案可能有帮助,但仍然没有找到源问题。如果解决得令人满意,我会更新我的发现。)
<updates...>
<更新...>
update:It just happened again and occurred on dragging/positioning of one XML file (Tomcats content.xml) underneath all other files. (Opened by "XML Editor": Provider: Eclipse Web Tools Platform
, Plug-in Name: XML editor
, Version: 1.0.700.v201005192212
, Plug-in Id: org.eclipse.wst.xmleditor.doc.user
)
更新:它又发生了,并发生在所有其他文件下面的一个 XML 文件 (Tomcats content.xml) 的拖动/定位。(由“XML 编辑器”打开: Provider: Eclipse Web Tools Platform
, Plug-in Name: XML editor
, Version: 1.0.700.v201005192212
, Plug-in Id: org.eclipse.wst.xmleditor.doc.user
)
update2:On further looking into it the error disappears when I move the editor back to the other files (all open editors in one area). Furthermore it appears only when entering or leaving this XML editor, not on e.g. making changes to it and saving it via CRTL+S. Other than that the JBoss-related exception from below occurs on the CTRL+S event, but independent of this issue (so it may not be related at all).
update2:当我将编辑器移回其他文件(一个区域中的所有打开的编辑器)时,进一步查看它时错误消失了。此外,它仅在进入或离开此 XML 编辑器时出现,而不是在例如对其进行更改并通过 CRTL+S 保存时出现。除此之外,CTRL+S 事件上发生了下面与 JBoss 相关的异常,但与此问题无关(因此它可能根本不相关)。
update3:Getting even closer: since some time there has been a new editor positioning feature around. (Initially I was a bit confused, but now I am getting the point and even visually can see what is meant and what makes the difference...). So there are two ways to position editors vertically or horizontally next to other editors:
更新 3:更接近:一段时间以来,出现了一个新的编辑器定位功能。(最初我有点困惑,但现在我明白了,甚至可以在视觉上看到是什么意思以及是什么造成了不同......)。因此,有两种方法可以将编辑器垂直或水平放置在其他编辑器旁边:
- positioning it inside the same "panel" (indicated by a global and two inner panels/borders/rectangles around the editors) and
- positing it next to the old "panel" (indicated by a rectangle frame around the old panel and the new one.
- 将其定位在同一个“面板”内(由编辑器周围的全局和两个内部面板/边框/矩形表示)和
- 将其放置在旧“面板”旁边(由旧面板和新面板周围的矩形框表示。
So putting an editor in a new "global" panel (2.) works fine, putting it in a new "local" panel (1.) causes the issue(that's actually very helpful because I can still continue to work quite efficiently) (maybe somebody else could report this bug appropriately) (it also seems not related to the XML editor mentioned above since it also happens e.g. on property files)
因此,将编辑器放在新的“全局”面板 (2.) 中效果很好,将其放在新的“本地”面板 (1.) 中会导致问题(这实际上非常有帮助,因为我仍然可以继续非常有效地工作)(也许其他人可以适当地报告这个错误)(它似乎也与上面提到的 XML 编辑器无关,因为它也发生在例如属性文件上)
update 4:I am using Windows 7 in hibernate mode. Meaning I don't start my Eclipse too often. Now I realized that Eclipse itself had been started (looking at the Task Manager) 2 times(visually and using ALT+TAB for open windows navigation this was not obvious). After (stopping/killing all open instances and) restarting the problem does not occur anymore.
更新 4:我在休眠模式下使用 Windows 7。这意味着我不会经常启动我的 Eclipse。现在我意识到Eclipse 本身已经启动(查看任务管理器)2 次(在视觉上并使用 ALT+TAB 进行打开的窗口导航这并不明显)。在(停止/杀死所有打开的实例并)重新启动后,问题不再发生。
update 5:In this duplicate question somebody stated it would have been solved by the latest windows update: https://stackoverflow.com/a/19316804/1915920. I'll check this out for myself, but currently I cannot reproduce the problem anyways.
更新 5:在这个重复的问题中,有人说它会被最新的 Windows 更新解决:https: //stackoverflow.com/a/19316804/1915920。我会亲自检查一下,但目前我无论如何都无法重现该问题。
update 6:In another situation I had this and it seemed related to some property window (in this case Jasper Reports) that updated its content automatically, based on the current editor (like an outline view). So it could be a good idea to close and re-open (all) outline and/or property windows.
更新 6:在另一种情况下,我遇到了这个问题,它似乎与某些属性窗口(在本例中为 Jasper Reports)有关,该窗口根据当前编辑器(如大纲视图)自动更新其内容。因此,关闭并重新打开(所有)大纲和/或属性窗口可能是一个好主意。
</...updates>
</...更新>
The error in general indicates, that some program(s) have (propably) unusually many (probably thousands?) of operating system file handles open. So one should check if outside or inside of Eclipse a lot of files are opened at the same time or opened over a short period of time, but not properly closed (they could be visually closed, but the operating system still thinks they are beeing used because the application did not properly free the file handles somehow).
该错误通常表明,某些程序(可能)异常多(可能是数千?)操作系统文件句柄打开。所以应该检查Eclipse的外部或内部是否有大量文件同时打开或在短时间内打开,但没有正确关闭(它们可以在视觉上关闭,但操作系统仍然认为它们正在被使用因为应用程序没有以某种方式正确释放文件句柄)。
Now I have this issue currently as well. If I look in the Error Log (Window->Show View->General->Error Log) I can see a lot of the following org.jboss.ide.eclipse.archives.core.* exceptions immediately before. Since I don't use the installed JBoss Developer Studio Plugin (that is likely related to this one) right now and no associated window or editor is opened (only some toolbar "JBoss Central" and perspective "JBoss" buttons) I'll have a look if disabling these will help on this sporadic problem. Also I closed all open editors, restarted Eclipse and open them and can't see this issue right now again.
现在我现在也有这个问题。如果我查看错误日志(窗口-> 显示视图-> 常规-> 错误日志),我可以在之前看到很多以下 org.jboss.ide.eclipse.archives.core.* 异常。由于我现在不使用已安装的 JBoss Developer Studio 插件(可能与此插件有关)并且没有打开关联的窗口或编辑器(只有一些工具栏“JBoss Central”和透视图“JBoss”按钮),我将有看看禁用这些是否有助于解决这个零星问题。此外,我关闭了所有打开的编辑器,重新启动 Eclipse 并打开它们,现在再也看不到这个问题了。
Problems occurred when invoking code from plug-in: "org.eclipse.core.resources".
...
...
java.lang.NullPointerException
at org.jboss.ide.eclipse.archives.core.WorkspaceChangeListener.visit(WorkspaceChangeListener.java:74)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
at org.jboss.ide.eclipse.archives.core.WorkspaceChangeListener.resourceChanged(WorkspaceChangeListener.java:70)
at org.eclipse.core.internal.events.NotificationManager.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:396)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1531)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2354)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
at org.eclipse.ui.internal.editors.text.WorkspaceOperationRunner.run(WorkspaceOperationRunner.java:75)
at org.eclipse.ui.internal.editors.text.WorkspaceOperationRunner.run(WorkspaceOperationRunner.java:65)
at org.eclipse.ui.editors.text.TextFileDocumentProvider.executeOperation(TextFileDocumentProvider.java:456)
at org.eclipse.ui.editors.text.TextFileDocumentProvider.saveDocument(TextFileDocumentProvider.java:772)
at org.eclipse.ui.texteditor.AbstractTextEditor.performSave(AbstractTextEditor.java:5068)
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.jboss.tools.common.editor.ObjectMultiPageEditor.saveX(ObjectMultiPageEditor.java:403)
at org.jboss.tools.common.editor.ObjectMultiPageEditor.doSave(ObjectMultiPageEditor.java:385)
at org.eclipse.ui.internal.SaveableHelper.run(SaveableHelper.java:150)
at org.eclipse.ui.internal.SaveableHelper.run(SaveableHelper.java:276)
at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1812)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:1809)
at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:284)
at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:263)
at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:155)
at org.eclipse.ui.internal.WorkbenchPage.saveSaveable(WorkbenchPage.java:3777)
at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3790)
at org.jboss.tools.common.model.ui.texteditors.SaveAction3.run(PropertiesTextEditorComponent.java:357)
at org.eclipse.jface.action.Action.runWithEvent(Action.java:499)
at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:119)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.GeneratedMethodAccessor58.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:285)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:504)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:555)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:376)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.accesseclipse.buildId=4.3.0.I20130605-2000
java.version=1.7.0_25
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.epp.package.reporting.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.reporting.product
(KeyBindingDispatcher.java:322)
at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:84)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1262)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1056)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1081)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1066)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1108)
at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1104)
at org.eclipse.swt.widgets.Widget.wmChar(Widget.java:1525)
at org.eclipse.swt.widgets.Control.WM_CHAR(Control.java:4723)
at org.eclipse.swt.widgets.Canvas.WM_CHAR(Canvas.java:344)
at org.eclipse.swt.widgets.Control.windowProc(Control.java:4611)
at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:340)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4977)
at org.eclipse.swt.internal.win32.OS.DispatchMessageW(Native Method)
at org.eclipse.swt.internal.win32.OS.DispatchMessage(OS.java:2549)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1113)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:610)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
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(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:636)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
...
...
Apache Directory Studio LDAP Browser 2.0.0.v20130628 org.apache.directory.studio.ldapbrowser.feature.feature.group Apache Software Foundation
DevUtilsFeature 1.0.9.201209201734 DevUtilsFeature.feature.group null
Eclipse IDE for Java and Report Developers 2.0.0.20130613-0530 epp.package.reporting null
GlassFish Tools 6.2.0.201307232054 oracle.eclipse.tools.glassfish.feature.group Oracle
JarPlug 0.6.1 com.simontuffs.eclipse.jarplug.feature.feature.group simontuffs.com
Jaspersoft Studio feature 5.2.0 com.jaspersoft.studio.feature.feature.group Jaspersoft Corporation
Java EE 5 Documentation 6.2.0.201307232054 oracle.eclipse.tools.javaee.doc.v5.feature.group Oracle
Java EE 6 Documentation 6.2.0.201307232054 oracle.eclipse.tools.javaee.doc.v6.feature.group Oracle
Java EE 7 Documentation 6.2.0.201307232054 oracle.eclipse.tools.javaee.doc.v7.feature.group Oracle
JBoss Developer Studio (Core Features) 7.0.0.GA-v20130720-0044-B364 com.jboss.jbds.product.feature.feature.group JBoss by Red Hat
Log Viewer Feature 0.9.8.8 de.anbos.eclipse.logviewer.feature.feature.group Andre Bossert
MercurialEclipse 2.1.0.201304290948 mercurialeclipse.feature.group MercurialEclipse project
MyLV 1.0.4 mylv_feature.feature.group null
Oracle ADF Documentation (11.1.1.4) 6.2.0.201307232054 oracle.eclipse.tools.adf.doc.v11114.feature.group Oracle
Oracle ADF Documentation (11.1.1.5) 6.2.0.201307232054 oracle.eclipse.tools.adf.doc.v11115.feature.group Oracle
Oracle ADF Documentation (11.1.1.6) 6.2.0.201307232054 oracle.eclipse.tools.adf.doc.v11116.feature.group Oracle
Oracle ADF Documentation (11.1.1.7) 6.2.0.201307232054 oracle.eclipse.tools.adf.doc.v11117.feature.group Oracle
Oracle ADF Documentation (12.1.2) 6.2.0.201307232054 oracle.eclipse.tools.adf.doc.v1212.feature.group Oracle
Oracle ADF Tools 6.2.0.201307232054 oracle.eclipse.tools.adf.feature.group Oracle
Oracle Cloud Tools 6.2.0.201307232054 oracle.eclipse.tools.cloud.feature.group Oracle
Oracle Coherence Tools 6.2.0.201307232054 oracle.eclipse.tools.coherence.feature.group Oracle
Oracle Database Tools 6.2.0.201307232054 oracle.eclipse.tools.database.feature.group Oracle
Oracle Java EE Tools 6.2.0.201307232054 oracle.eclipse.tools.javaee.feature.group Oracle
Oracle Maven Tools 6.2.0.201307232054 oracle.eclipse.tools.maven.feature.group Oracle
Oracle Spring Tools 6.2.0.201307232054 oracle.eclipse.tools.spring.feature.group Oracle
Oracle WebLogic Scripting Tools 6.2.0.201307232054 oracle.eclipse.tools.weblogic.scripting.feature.group Oracle
Oracle WebLogic Server Tools 6.2.0.201307232054 oracle.eclipse.tools.weblogic.feature.group Oracle
Toad? Extension for Eclipse - Community Edition - Core Plugin 1.8.3.201308140922 com.quest.toadext.core.feature.feature.group Quest Software, Inc.
Toad? Extension for Eclipse - Community Edition - MySQL DB Plugin 1.8.3.201308140922 com.quest.toadext.mysql.feature.feature.group Quest Software, Inc.
Toad? Extension for Eclipse - Community Edition - Oracle Database Plugin 1.8.3.201308140922 com.quest.toadext.feature.feature.group Quest Software, Inc.
Toad? Extension for Eclipse - Community Edition - PostgreSQL Plugin 1.8.3.201308140922 com.quest.toadext.postgre.feature.feature.group Quest Software, Inc.
installed plugins (Help->About Eclipse->Installation Details->Installed Software: mark all + CTRL+C): (Eclipse Kepler Java EE and BIRT edition as base install)
已安装的插件(Help->About Eclipse->Installation Details->Installed Software:标记全部 + CTRL+C):(Eclipse Kepler Java EE 和 BIRT 版本作为基础安装)
export GTK_IM_MODULE=ibus
回答by Vittee Nakka
For me, this causes by ATI Desktop Manager.
对我来说,这是由 ATI 桌面管理器引起的。
After killing "HydraDM.exe" process, the problem was gone. When I re-run it again, the problem return.
杀死“HydraDM.exe”进程后,问题就消失了。当我再次重新运行它时,问题又回来了。
So if you're using ATI Graphic Card, try to open Task Manager, locate "HydraDM.exe" (or 64 bit version) then kill it.
因此,如果您使用的是 ATI 显卡,请尝试打开任务管理器,找到“HydraDM.exe”(或 64 位版本)然后将其杀死。
回答by LukaszQr
If you use DisplayFusion:
如果您使用 DisplayFusion:
- Open Display Fusion settings page
- Click compatibility tab
- Add Eclipse or STS.exe application
- Check "Disable TitleBar Buttons (this application only), "Disable Application Hooks (this application only)", and "Use Process file icon on DisplayFusion taskbar, not window icon"
- 打开 Display Fusion 设置页面
- 单击兼容性选项卡
- 添加 Eclipse 或 STS.exe 应用程序
- 选中“禁用标题栏按钮(仅限此应用程序)、禁用应用程序挂钩(仅限此应用程序)”和“在 DisplayFusion 任务栏上使用进程文件图标,而不是窗口图标”
Reference: Display Fusion FIX
参考:显示融合修复
回答by Heiko
I had the exact same issue. I found here a solution which works for me : https://bugs.eclipse.org/bugs/show_bug.cgi?id=517671#c58
我有完全相同的问题。我在这里找到了一个对我有用的解决方案:https: //bugs.eclipse.org/bugs/show_bug.cgi?id=517671#c58
For me it was sufficient to put
对我来说就足够了
##代码##into ~/.profile.
进入 ~/.profile。
Hope this will help some of you also.
希望这也能帮助你们中的一些人。
回答by Andras Balázs Lajtha
If you have a fresh Windows 7, force a Windows Update. That will make the problem go away. It's a shot in the dark, but solved my problem. I struggled with it for a day until I realized that newer eclipse releases give the above error with older .net Framework: everything went fine until a driver installed .net 4.0, and from that point Eclipse editor gave the unhandled event loop exception.
如果您使用的是全新的 Windows 7,请强制执行 Windows 更新。这将使问题消失。这是黑暗中的一个镜头,但解决了我的问题。我为此苦苦挣扎了一天,直到我意识到较新的 Eclipse 版本会在较旧的 .net 框架中出现上述错误:一切正常,直到驱动程序安装了 .net 4.0,并且从那时起 Eclipse 编辑器给出了未处理的事件循环异常。