Community
Participate
Working Groups
I20101109-0800 Cocoa 32-bit build. Steps to reproduce: 1) start eclipse without specifying -data <workspace> 2) the workspace chooser dialog is shown. 3) click on browse button to bring up finder. 4) click around in finder a bit and notice the UI hangs On my system the UI thread is spinning the CPU and stuck in org.eclipse.swt.internal.cocoa.OS.objc_msgSend Daemon Thread [Thread-0] (Suspended) org.eclipse.swt.internal.cocoa.OS.objc_msgSend(int, int, int, int) line: not available [native method] org.eclipse.swt.internal.cocoa.NSOpenPanel(org.eclipse.swt.internal.cocoa.NSSavePanel).runModalForDirectory(org.eclipse.swt.internal.cocoa.NSString, org.eclipse.swt.internal.cocoa.NSString) line: 37 org.eclipse.swt.widgets.DirectoryDialog.open() line: 146 org.eclipse.ui.internal.ide.ChooseWorkspaceDialog$3.widgetSelected(org.eclipse.swt.events.SelectionEvent) line: 285 org.eclipse.swt.widgets.TypedListener.handleEvent(org.eclipse.swt.widgets.Event) line: 234 org.eclipse.swt.widgets.EventTable.sendEvent(org.eclipse.swt.widgets.Event) line: 84 org.eclipse.swt.widgets.Display.sendEvent(org.eclipse.swt.widgets.EventTable, org.eclipse.swt.widgets.Event) line: 3963 org.eclipse.swt.widgets.Button(org.eclipse.swt.widgets.Widget).sendEvent(org.eclipse.swt.widgets.Event) line: 1431 org.eclipse.swt.widgets.Button(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event, boolean) line: 1454 org.eclipse.swt.widgets.Button(org.eclipse.swt.widgets.Widget).sendEvent(int, org.eclipse.swt.widgets.Event) line: 1439 org.eclipse.swt.widgets.Button(org.eclipse.swt.widgets.Widget).notifyListeners(int, org.eclipse.swt.widgets.Event) line: 1251 org.eclipse.swt.widgets.Display.runDeferredEvents() line: 3809 org.eclipse.swt.widgets.Display.readAndDispatch() line: 3462 org.eclipse.ui.internal.ide.ChooseWorkspaceDialog(org.eclipse.jface.window.Window).runEventLoop(org.eclipse.swt.widgets.Shell) line: 825 org.eclipse.ui.internal.ide.ChooseWorkspaceDialog(org.eclipse.jface.window.Window).open() line: 801 org.eclipse.ui.internal.ide.ChooseWorkspaceDialog.prompt(boolean) line: 91 org.eclipse.ui.internal.ide.application.IDEApplication.promptForWorkspace(org.eclipse.swt.widgets.Shell, org.eclipse.ui.internal.ide.ChooseWorkspaceData, boolean) line: 277 org.eclipse.ui.internal.ide.application.IDEApplication.checkInstanceLocation(org.eclipse.swt.widgets.Shell) line: 225 org.eclipse.ui.internal.ide.application.IDEApplication.start(org.eclipse.equinox.app.IApplicationContext) line: 105 org.eclipse.equinox.internal.app.EclipseAppHandle.run(java.lang.Object) line: 196 org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(java.lang.Object) line: 110 org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(java.lang.Object) line: 79 org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.Object) line: 369 org.eclipse.core.runtime.adaptor.EclipseStarter.run(java.lang.String[], java.lang.Runnable) line: 179 sun.reflect.NativeMethodAccessorImpl.invoke0(java.lang.reflect.Method, java.lang.Object, java.lang.Object[]) line: not available [native method] sun.reflect.NativeMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 39 sun.reflect.DelegatingMethodAccessorImpl.invoke(java.lang.Object, java.lang.Object[]) line: 25 java.lang.reflect.Method.invoke(java.lang.Object, java.lang.Object...) line: 592 org.eclipse.equinox.launcher.Main.invokeFramework(java.lang.String[], java.net.URL[]) line: 621 org.eclipse.equinox.launcher.Main.basicRun(java.lang.String[]) line: 576 org.eclipse.equinox.launcher.Main.run(java.lang.String[]) line: 1409 org.eclipse.equinox.launcher.Main.main(java.lang.String[]) line: 1385
If you can reproduce this, open up a Terminal window and run sample on the process: % sample <PID of hung process> 2 20 Then, attach the dump to the bug. This is almost always a bad remote mount point.
Created attachment 183240 [details] sample dump
Created attachment 183241 [details] sample dump 2
The first dump I caused by click the drop down in the workspace chooser instead of using the Browse button. The second dump I caused by clicking the Browse button and navigating the finder a bit.
I have tried to reproduce this on 3.6 with the same machine but have not been successful.
I'll see what I can do to reproduce it. Both sample traces show we're stuck inside AppKit and not the SWT.
I should have mentioned this before. I am using 10.5.8 Mac OS X. I am mentioning this because I saw you post a note about some conditional check for 10.5 vs 10.6 to the releng list.
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. If you have further information on the current state of the bug, please add it. 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.
This was reported on Mac 10.5 and Eclipse 3.7. Closing it as I'm unable to reproduce this with Eclipse 4.10 and macOS 10.14. Also, there are no reports of Directory Dialog hang for a long time.
