Community
Participate
Working Groups
Some times when debug tomcat application with eclipse CPU load to 400% and never stops. I get this trace from yourkit profiler. Frozen threads found (potential deadlock) It seems that the following threads have not changed their stack for more than 10 seconds. These threads are possibly (but not necessarily!) in a deadlock or hung. main <--- Frozen for at least 1m 3 sec org.eclipse.swt.internal.cocoa.OS.objc_msgSend_bool(long, long, long, long) org.eclipse.swt.internal.cocoa.NSRunLoop.runMode(NSString, NSDate) org.eclipse.swt.widgets.Display.sleep() org.eclipse.ui.application.WorkbenchAdvisor.eventLoopIdle(Display) org.eclipse.ui.internal.ide.application.IDEWorkbenchAdvisor.eventLoopIdle(Display) org.eclipse.ui.internal.Workbench$3.eventLoopIdle(Display) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run() org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(MApplicationElement, IEclipseContext) org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(MApplicationElement) org.eclipse.ui.internal.Workbench$5.run() org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm, Runnable) org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) org.eclipse.ui.PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) org.eclipse.ui.internal.ide.application.IDEApplication.start(IApplicationContext) org.eclipse.equinox.internal.app.EclipseAppHandle.run(Object) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Object) org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Object) org.eclipse.core.runtime.adaptor.EclipseStarter.run(Object) org.eclipse.core.runtime.adaptor.EclipseStarter.run(String[], Runnable) sun.reflect.NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) sun.reflect.NativeMethodAccessorImpl.invoke(Object, Object[]) sun.reflect.DelegatingMethodAccessorImpl.invoke(Object, Object[]) java.lang.reflect.Method.invoke(Object, Object[]) org.eclipse.equinox.launcher.Main.invokeFramework(String[], URL[]) org.eclipse.equinox.launcher.Main.basicRun(String[]) org.eclipse.equinox.launcher.Main.run(String[])
Moving to SWT
There is not much information here for us to debug or investigate, can you please provide more details including exact versions of Eclipse and Mac OS as well as a sample program or plugin that can be used to reproduce the freeze in Eclipse. As for the stack trace itself, I'm not sure if it indicates anything wrong as the last call made in SWT is to Display.sleep() and it is natural that the thread stack won't update after that until there is an event which causes it to wake up. Now why that wake up event is not happening could be an entirely different and unrelated problem. Essentially, without a reproducible scenario within Eclipse or SWT, there isn't much to do here. Thanks!
Created attachment 241050 [details] eclipse log file OS X 10.8.5 Version: Kepler Service Release 2 Build id: 20140224-0627 Dali Java Persistence Tools - EclipseLink DBWS Support Version: 1.2.2.v201401172016-797J4CcNBHPCpEqBjYXMNGD Build id: 20120913000254 I'll try catch such bug snapshot
Created attachment 241051 [details] snapshot yourkit snaphot of eclipse freezed
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
