--- Comment #5 from Carsten Reckord <email address hidden> ---
I don't see anything in those traces that indicates the Marketplace Client's
invlovement in this.
(There are two stack frames below the current ui event loop on the main thread
in the first two dumps, but that looks coincidental, especially since the
latest thread dump doesn't contain MPC frames at all.)
What I do see in those traces are an awful lot of threads waiting for a
Display.syncExec to return:
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> - waiting on <0x00000000c38b8b48> (a org.eclipse.swt.widgets.RunnableLock)
> at java.lang.Object.wait(Object.java:503)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:199)
> - locked <0x00000000c38b8b48> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4633)
while at the same time, the main thread seems to be idling:
> "main" prio=10 tid=0x00007f74d000a000 nid=0x1847 runnable [0x00007f74d8ed3000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2425)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.block(ModalContext.java:172)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:387)
This could be a bug in SWT under Linux/GTK. Reassigning to the SWT team.
Hello, thanks for looking at this. I believe it is a problem with GTK as I also tried eclipse and it too, was hanging.
Please see the bug report from eclipse:
https:/ /bugs.eclipse. org/bugs/ show_bug. cgi?id= 485808
Product/Component: Platform / SWT
Carsten Reckord <email address hidden> changed:
What |Removed |Added ------- ------- ------- ------- ------- ------- ------- ------- ------- ------
CC| |<email address hidden>
Component| Install |SWT
Version| unspecified |4.5
Assignee| <email address hidden> |platform- swt-inbox@ eclipse.
|rg |org
Product| MPC |Platform
-------
--- Comment #5 from Carsten Reckord <email address hidden> ---
I don't see anything in those traces that indicates the Marketplace Client's
invlovement in this.
(There are two stack frames below the current ui event loop on the main thread
in the first two dumps, but that looks coincidental, especially since the
latest thread dump doesn't contain MPC frames at all.)
What I do see in those traces are an awful lot of threads waiting for a
Display.syncExec to return:
> java.lang. Thread. State: WAITING (on object monitor) Object. wait(Native Method) 8b48> (a org.eclipse. swt.widgets. RunnableLock) Object. wait(Object. java:503) swt.widgets. Synchronizer. syncExec( Synchronizer. java:199) 8b48> (a org.eclipse. swt.widgets. RunnableLock) ui.internal. UISynchronizer. syncExec( UISynchronizer. java:145) swt.widgets. Display. syncExec( Display. java:4633)
> at java.lang.
> - waiting on <0x00000000c38b
> at java.lang.
> at org.eclipse.
> - locked <0x00000000c38b
> at org.eclipse.
> at org.eclipse.
while at the same time, the main thread seems to be idling:
> "main" prio=10 tid=0x00007f74d 000a000 nid=0x1847 runnable [0x00007f74d8ed 3000] Thread. State: RUNNABLE swt.internal. gtk.OS. _g_main_ context_ iteration( Native Method) swt.internal. gtk.OS. g_main_ context_ iteration( OS.java: 2425) swt.widgets. Display. readAndDispatch (Display. java:3428) jface.operation .ModalContext$ ModalContextThr ead.block( ModalContext. java:172) jface.operation .ModalContext. run(ModalContex t.java: 387)
> java.lang.
> at org.eclipse.
> at org.eclipse.
> at org.eclipse.
> at org.eclipse.
> at org.eclipse.
This could be a bug in SWT under Linux/GTK. Reassigning to the SWT team.