Community
Participate
Working Groups
Have plugin that includes Ant tasks in JAR that do not rely on Eclipse runtime. Launch such a task from Eclipse Wait for eternity or abort eclipse This behavior is new to Eclipse 3.7.1 as I can run the exact same task using Eclipse 3.6.2. Is it related to the use of Ant 1.8 instead of 1.7 in Indigo?
Created attachment 206163 [details] hang both in Eclipse JVM and external JVM
Maybe related to bug#34466 ?
I experienced the same behaviour with FDT4 max installed (a flex/actioscript plugin that includes ant tasks), by starting an ant target as the first thing to do after eclipse starts up in the normal perspective that is supplied by the fdt-plugin. Testing with another eclipse installation without fdt, I found that I can work around the hang during "Perform pre-launch check", by opening the default java-perspective and running a simple ant target that doesn't depend on any plugin tasks (like a simple target with an echo task). Subsequent attempts at replicating the hang-up with fdt as the start-up perspective has failed. Hope this can help
Can you take a stack dump and attach it here the next time Eclipse hangs up? http://wiki.eclipse.org/How_to_report_a_deadlock
Started using console with arguments to create thread dumps: QuadBox:eclipse-37RC4 maarten$ ./eclipse -console -consoleLog osgi> org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. !SESSION 2011-10-31 22:46:07.535 ----------------------------------------------- eclipse.buildId=M20110909-1335 java.version=1.6.0_26 java.vendor=Apple Inc. BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US Framework arguments: -product org.eclipse.epp.package.rcp.product Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product org.eclipse.epp.package.rcp.product -console -consoleLog !ENTRY org.eclipse.core.resources 2 10035 2011-10-31 22:46:09.014 !MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes. org.eclipse.m2e.logback.configuration: Logback config file: /Users/maarten/Workspaces/workspace-fold1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.0.100.20110804-1717.xml org.eclipse.m2e.logback.configuration: Initializing logback org.eclipse.m2e.logback.configuration: eclipse.consoleLog=true !ENTRY org.eclipse.core.net 1 0 2011-10-31 22:46:10.014 !MESSAGE System property http.nonProxyHosts has been set to localhost|*.localhost|127.0.0.1|apple.com|*.apple.com|eclipse.org|*.eclipse.org|ingbank.nl|*.ingbank.nl|google.com|*.google.com by an external source. This value will be overwritten using the values from the preferences !ENTRY com.fold1.eulumdat.tools 1 0 2011-10-31 22:46:17.245 !MESSAGE com.fold1.eulumdat.tools.views.ProductPropertiesView created !ENTRY org.eclipse.jface 2 0 2011-10-31 22:46:17.975 !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation. !SUBENTRY 1 org.eclipse.jface 2 0 2011-10-31 22:46:17.975 !MESSAGE A conflict occurred for ALT+COMMAND+Q P: Binding(ALT+COMMAND+Q P, ParameterizedCommand(Command(org.eclipse.ui.views.showView,Show View, Shows a particular view, Category(org.eclipse.ui.category.views,Views,Commands for opening views,true), org.eclipse.ui.handlers.ShowViewHandler@c5d53c3, [Lorg.eclipse.ui.internal.commands.Parameter;@43262d8c,,true),[Lorg.eclipse.core.commands.Parameterization;@7f7864c4), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.ui.contexts.window,,cocoa,system) Binding(ALT+COMMAND+Q P, ParameterizedCommand(Command(org.eclipse.ui.views.showView,Show View, Shows a particular view, Category(org.eclipse.ui.category.views,Views,Commands for opening views,true), org.eclipse.ui.handlers.ShowViewHandler@c5d53c3, [Lorg.eclipse.ui.internal.commands.Parameter;@43262d8c,,true),[Lorg.eclipse.core.commands.Parameterization;@391fc13d), org.eclipse.ui.defaultAcceleratorConfiguration, org.eclipse.ui.contexts.window,,cocoa,system) Loading plugins from /Applications/eclipse-37RC4/plugins/org.lrg.insider.plugins_2.0.7/bin Loading Loading plugins from /Applications/eclipse-37RC4/plugins/com.intooitus.plugins_2.0.7/bin 212 plugins successfully loaded! 2011-10-31 22:46:20,459 [Worker-9] INFO org.mortbay.log - Logging to Logger[org.mortbay.log] via org.mortbay.log.Slf4jLog
Created attachment 206242 [details] Thread dump for bug 362399
Created attachment 206243 [details] Thread Dump before problem
Comment on attachment 206242 [details] Thread dump for bug 362399 this one is after the hang occurs
While the launch thread is trying to look for breakpoints, the wst debugger is also trying to get some breakpoints seems to be causing this. The threads in question are.. ######### "Worker-3" prio=5 tid=11d002000 nid=0x11f901000 in Object.wait() [11f900000] java.lang.Thread.State: RUNNABLE at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at java.lang.Class.newInstance0(Class.java:355) at java.lang.Class.newInstance(Class.java:308) at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184) at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905) at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243) at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55) at org.eclipse.debug.internal.core.BreakpointManager.createBreakpoint(BreakpointManager.java:527) at org.eclipse.debug.internal.core.BreakpointManager.loadBreakpoints(BreakpointManager.java:264) at org.eclipse.debug.internal.core.BreakpointManager.initializeBreakpoints(BreakpointManager.java:431) at org.eclipse.debug.internal.core.BreakpointManager.getBreakpoints0(BreakpointManager.java:400) - locked <790dbbeb0> (a org.eclipse.debug.internal.core.BreakpointManager) at org.eclipse.debug.internal.core.BreakpointManager.getBreakpoints(BreakpointManager.java:409) at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.getBreakpoints(AntLaunchDelegate.java:850) at org.eclipse.debug.core.model.LaunchConfigurationDelegate.preLaunchCheck(LaunchConfigurationDelegate.java:212) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:809) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703) at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:928) at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1132) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54 ########## Worker-6" prio=5 tid=11ae29800 nid=0x11fc0a000 waiting for monitor entry [11fc09000] java.lang.Thread.State: BLOCKED (on object monitor) at org.eclipse.debug.internal.core.BreakpointManager.getBreakpoints0(BreakpointManager.java:399) - waiting to lock <790dbbeb0> (a org.eclipse.debug.internal.core.BreakpointManager) at org.eclipse.debug.internal.core.BreakpointManager.getBreakpoints(BreakpointManager.java:385) at org.eclipse.debug.core.model.Breakpoint.<clinit>(Breakpoint.java:47) at org.eclipse.wst.jsdt.debug.internal.core.JavaScriptPreferencesManager.createSuspendOnException(JavaScriptPreferencesManager.java:168) at org.eclipse.wst.jsdt.debug.internal.core.JavaScriptPreferencesManager.access$2(JavaScriptPreferencesManager.java:166) at org.eclipse.wst.jsdt.debug.internal.core.JavaScriptPreferencesManager$StartJob.run(JavaScriptPreferencesManager.java:80) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) #########
(In reply to comment #9) > While the launch thread is trying to look for breakpoints, the wst debugger is > also trying to get some breakpoints seems to be causing this. Yup, this is a dupe of bug 345298 (the breakpoint manager does not return from trying to load breakpoint extensions) *** This bug has been marked as a duplicate of bug 345298 ***
