| Linux GTK hanging in an RCP Application for java 6 [message #636149] |
Fri, 29 October 2010 13:28  |
 Tod Creasey
Messages: 59
Registered: July 2009 |
Member |
|
|
I have an RCP application that hangs when I open a DirectoryDialog on Java 6 only (no problem on Java 5) with both a Sun or IBM VM.
After my command is executed it runs the following code:
DirectoryDialog dialog = new DirectoryDialog(window.getShell());
dialog.open();
After the user selects Ok the dialog goes away and the UIThread becomes unresponsive.
This occurs in both 3.4.2 and 3.6.1
Here is the stack trace of the main Thread when it happens:
org.eclipse.equinox.launcher.Main at localhost:44027
Thread [main] (Suspended)
OS._g_main_context_iteration(int, boolean) line: not available [native method]
OS.g_main_context_iteration(int, boolean) line: 2229
Display.readAndDispatch() line: 3159
Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
Workbench.runUI() line: 2604
Workbench.access$4(Workbench) line: 2438
Workbench$7.run() line: 671
Realm.runWithDefault(Realm, Runnable) line: 332
Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
Application.start(IApplicationContext) line: 52
EclipseAppHandle.run(Object) line: 196
EclipseAppLauncher.runApplication(Object) line: 110
EclipseAppLauncher.start(Object) line: 79
EclipseStarter.run(Object) line: 369
EclipseStarter.run(String[], Runnable) line: 179
NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method]
NativeMethodAccessorImpl.invoke(Object, Object[]) line: 48
DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25
Method.invoke(Object, Object...) line: 600
Main.invokeFramework(String[], URL[]) line: 619
Main.basicRun(String[]) line: 574
Main.run(String[]) line: 1407
Main.main(String[]) line: 1383
Daemon Thread [Signal Dispatcher] (Running)
Daemon Thread [State Data Manager] (Running)
Daemon Thread [Start Level Event Dispatcher] (Running)
Daemon Thread [Framework Event Dispatcher] (Running)
Thread [Worker-JM] (Running)
Daemon Thread [AWT-XAWT] (Running)
Thread [Worker-0] (Running)
Thread [Worker-1] (Running)
Thread [Worker-2] (Running)
|
|
|
| Re: Linux GTK hanging in an RCP Application for java 6 [message #636485 is a reply to message #636149] |
Mon, 01 November 2010 14:36  |
Grant Gayed
Messages: 2150
Registered: July 2009 |
Senior Member |
|
|
This sounds like https://bugs.eclipse.org/bugs/show_bug.cgi?id=312137 . He
didn't mention jre5 vs jre6, and you didn't mention leaving the input field
blank, but I'm guessing it's the same problem (?).
Grant
"Tod Creasey" <Tod_Creasey@ca.ibm.com> wrote in message
news:iaei05$gen$1@news.eclipse.org...
>I have an RCP application that hangs when I open a DirectoryDialog on Java
>6 only (no problem on Java 5) with both a Sun or IBM VM.
>
> After my command is executed it runs the following code:
>
> DirectoryDialog dialog = new DirectoryDialog(window.getShell());
> dialog.open();
>
> After the user selects Ok the dialog goes away and the UIThread becomes
> unresponsive.
>
> This occurs in both 3.4.2 and 3.6.1
>
> Here is the stack trace of the main Thread when it happens:
> org.eclipse.equinox.launcher.Main at localhost:44027 Thread [main]
> (Suspended) OS._g_main_context_iteration(int, boolean) line: not available
> [native method] OS.g_main_context_iteration(int, boolean) line: 2229
> Display.readAndDispatch() line: 3159
> Workbench.runEventLoop(Window$IExceptionHandler, Display) line: 2640
> Workbench.runUI() line: 2604 Workbench.access$4(Workbench) line: 2438
> Workbench$7.run() line: 671 Realm.runWithDefault(Realm, Runnable) line:
> 332 Workbench.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 664
> PlatformUI.createAndRunWorkbench(Display, WorkbenchAdvisor) line: 149
> Application.start(IApplicationContext) line: 52
> EclipseAppHandle.run(Object) line: 196
> EclipseAppLauncher.runApplication(Object) line: 110
> EclipseAppLauncher.start(Object) line: 79 EclipseStarter.run(Object) line:
> 369 EclipseStarter.run(String[], Runnable) line: 179
> NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not
> available [native method] NativeMethodAccessorImpl.invoke(Object,
> Object[]) line: 48 DelegatingMethodAccessorImpl.invoke(Object, Object[])
> line: 25 Method.invoke(Object, Object...) line: 600
> Main.invokeFramework(String[], URL[]) line: 619 Main.basicRun(String[])
> line: 574 Main.run(String[]) line: 1407 Main.main(String[]) line: 1383
> Daemon Thread [Signal Dispatcher] (Running) Daemon Thread [State Data
> Manager] (Running) Daemon Thread [Start Level Event Dispatcher] (Running)
> Daemon Thread [Framework Event Dispatcher] (Running) Thread [Worker-JM]
> (Running) Daemon Thread [AWT-XAWT] (Running) Thread [Worker-0] (Running)
> Thread [Worker-1] (Running) Thread [Worker-2] (Running)
>
|
|
|
Powered by
FUDForum. Page generated in 0.01677 seconds
] 
Search
Help
Register
Login
Home
