Community
Participate
Working Groups
Build Identifier: 20110916-0149 I'm using awesome (https://awesome.naquadah.org/) as window manager, when i start eclipse and don't give focus to it, eclipse uses 100% and start up is not finished. As soon as i switch to the eclipse tag (even it is for only 1 second), eclipse shows the editor window etc. and everything works normal from now on. eclipse is automatically starting on another workspace/tag with my config. workaround is to give focus to eclipse once. Reproducible: Always Steps to Reproduce: 1. use tiling windowmanager 2. start eclipse (on other workspace/tag) 3. dp not give focus to eclipse
Not sure where to start with this. Moving to SWT to see if they have had any experience with "awesome".
See http://wiki.eclipse.org/index.php/How_to_report_a_deadlock for steps on how to find out what Eclipse is doing. PW
Created attachment 207750 [details] thread dump of hanging eclipse, which did not get displayed after splash screen 1) Indigo Service Release 1, 20110916-0149 2) [~]> java -version java version "1.6.0_29" Java(TM) SE Runtime Environment (build 1.6.0_29-b11) Java HotSpot(TM) Server VM (build 20.4-b02, mixed mode) 3) startup Eclipse, and switch workspace before editor is shown 4) yes start eclipse switch workspace, "do not allow eclipse to show up" 5) see attachment The bad boy is: at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) (seen in Sampler)
There have been several variations of this bug from this time period. I cannot reproduce the issue, and the latest SWT hang we had was a webkit1 problem. Closing this ticket, please re-open if it if you experience the bug on GTK3.22 with 4.8. GTK3.22/4.8 M7/Fedora 28.
