Bug 470324 - Crash / Wont Launch
Summary: Crash / Wont Launch
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 4.5   Edit
Hardware: PC Linux
: P3 blocker (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2015-06-17 00:52 EDT by Peter Carlson CLA
Modified: 2015-08-12 12:56 EDT (History)
5 users (show)

See Also:


Attachments
.ini .sh and .log (10.64 KB, application/x-tar)
2015-06-17 00:52 EDT, Peter Carlson CLA
no flags Details
jstack trace (1.75 KB, text/plain)
2015-06-22 12:34 EDT, Peter Carlson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Carlson CLA 2015-06-17 00:52:49 EDT
Created attachment 254491 [details]
.ini .sh and .log

Eclipse is hanging at various stages when I launch. It always gets to the prompt of workspace dialog. After that sometimes it hangs immediately, sometimes it hangs on org...theme, sometimes it hangs on org...swt, sometimes it loads the main workspace window (consuming about 1/3rd x 1/3rd of my screen) and just stays grey, sometimes it loads the workspace window, maximizes, loads the toolbar and nothing else. Always it takes one of my 8 cores to 100%.

Afterwards, opening a new window, takes forever. I can switch to email, but I can change to a new email. I can switch to the browser, but I cant switch tabs. I can switch to my terminal, but I cant open a new terminal. Recovery is only by killing the java process at which point I can operate my system normally again.

I have tried Kepler, Luna and Mars. Same result. 
I have tried clearing the workspace/.metadata/.plugins folder
I have removed all traces of eclipse and re-installed
I have tried installing eclipse for only myself (under my home directory)
I have tried openjdk7 and 8 as well as oracle jdk 7 and 8
I have tried adding --launcher.GTK_version 2 to eclipse.ini
I have tried launching eclipse using a script with export SWT_GTK3=0
I have tried using NVIDIA drivers and nouveau, no change
I have tried the standard adwaita theme as well as other themes

I have been running eclipse for quite some time on my desktop (kepler and earier versions) and I run luna on my laptop which is the same OS install, not sure what broke my desktop nor why it still runs on my laptop

OS is ubuntu 15.04, Gnome 3.14.4  (and Gnome 3.16)
Comment 1 Andrey Loskutov CLA 2015-06-17 00:58:10 EDT
While Eclipse hangs, please run

jps
jstack <pid from jps above>

commands and attach the stack trace here.
Comment 2 Lars Vogel CLA 2015-06-17 01:25:48 EDT
Mars works well for me with Ubuntu 15.04, I use it since the Ubuntu release.  I'm not aware of this launcher setting you are using but to enforce GTK2 I use:

export swt_gtk3=0

But in general GTK3 works fine for me with the latest I-Build of Eclipse. Can you post your I-Build number? Ctrl+3 -> Copy Build id to Clipboard
Comment 3 Peter Carlson CLA 2015-06-22 12:34:54 EDT
Created attachment 254610 [details]
jstack trace

ok, I have done more testing, sorry it took so long.

I upgraded to gnome 3.16 and mars runs with no problems.  I did a ppa-purge of gnome3-staging and went back to 3.14 and the hang re-appears.

I cant currently stay on 3.16 as there are other issues with 3.16 - there are serious visual defects on my computer using it.

Sadly the stack trace probably wont help as it's not a stack trace of eclipse, but rather an error saying the debugger cant attach.

Peter
Comment 4 Peter Carlson CLA 2015-07-12 12:25:46 EDT
The problem has now appeared on 3.16.  I am not sure what changed in the past couple of days.  I am now completely unable to run eclipse
Comment 5 Peter Carlson CLA 2015-07-12 14:08:23 EDT
and here is my eclipse log and syslogs

syslog:
Jul 12 11:05:30 office gnome-session[1747]: Window manager warning: Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp
Jul 12 11:05:30 office gnome-session[1747]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1802084 (eclipse)
Jul 12 11:05:34 office gnome-session[1747]: (gnome-terminal.real:5097): Gtk-WARNING **: Error setting gtk-primary-button-warps-slider in /home/peter/.config/gtk-3.0/settings.ini: Key file contains key 'gtk-primary-button-warps-slider' which has a value that cannot be interpreted.
Jul 12 11:05:34 office gnome-session[1747]: (gnome-terminal.real:5097): Gtk-WARNING **: Error setting gtk-primary-button-warps-slider in /home/peter/.config/gtk-3.0/settings.ini: Key file contains key 'gtk-primary-button-warps-slider' which has a value that cannot be interpreted.
Jul 12 11:05:41 office gnome-session[1747]: Window manager warning: Window 0x6000003 (Eclipse) sets an MWM hint indicating it isn't resizable, but sets min size 452 x 302 and max size 2147483647 x 2147483647; this doesn't make much sense.
Jul 12 11:05:42 office gnome-session[1747]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x6000003 (Eclipse )
Jul 12 11:06:22 office acpid: client 1514[0:0] has disconnected
Jul 12 11:06:37 office acpid: client connected from 1514[0:0]
Jul 12 11:06:37 office acpid: 1 client rule loaded
Jul 12 11:06:49 office gnome-session[1747]: (nemo:2581): Gtk-CRITICAL **: gtk_widget_get_realized: assertion 'GTK_IS_WIDGET (widget)' failed
Jul 12 11:06:49 office gnome-session[1747]: (nemo:2581): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion 'GTK_IS_WIDGET (widget)' failed
Jul 12 11:06:49 office gnome-session[1747]: sys:1: Warning: g_hash_table_contains: assertion 'hash_table != NULL' failed
Jul 12 11:06:49 office gnome-session[1747]: sys:1: Warning: g_hash_table_insert_internal: assertion 'hash_table != NULL' failed

eclipse.log
!SESSION 2015-07-12 11:05:35.101 -----------------------------------------------
eclipse.buildId=4.5.0.I20150528-0700
java.version=1.8.0_45
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_us_US
Framework arguments:  -product org.eclipse.epp.package.jee.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product

!ENTRY org.eclipse.jface 2 0 2015-07-12 11:05:43.401
!MESSAGE Keybinding conflicts occurred.  They may interfere with normal accelerator operation.
!SUBENTRY 1 org.eclipse.jface 2 0 2015-07-12 11:05:43.401
!MESSAGE A conflict occurred for ALT+CTRL+U:
Binding(ALT+CTRL+U,
	ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.search.occurrences.in.file.quickMenu,Show Occurrences in File Quick Menu,
		Shows the Occurrences in File quick menu,
		Category(org.eclipse.search.ui.category.search,Search,Search command category,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@2cca7d3c,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,gtk,system)
Binding(ALT+CTRL+U,
	ParameterizedCommand(Command(com.jaspersoft.studio.server.publish,Publish the file on JasperReports Server,
		,
		Category(org.eclipse.core.commands.categories.autogenerated,Uncategorized,Commands that were either auto-generated or have no category,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5e1535e0,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)
Binding(ALT+CTRL+U,
	ParameterizedCommand(Command(org.eclipse.team.svn.ui.command.UpdateCommand,Update,
		,
		Category(org.eclipse.team.svn.ui.command.category,SVN,null,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@6c27be1d,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)
!SUBENTRY 1 org.eclipse.jface 2 0 2015-07-12 11:05:43.401
!MESSAGE A conflict occurred for ALT+CTRL+T:
Binding(ALT+CTRL+T,
	ParameterizedCommand(Command(org.eclipse.tm.terminal.connector.local.command.launch,Open Local Terminal on Selection,
		,
		Category(org.eclipse.tm.terminal.view.ui.commands.category,Terminal Commands,null,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@2e7cd4bb,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)
Binding(ALT+CTRL+T,
	ParameterizedCommand(Command(org.eclipse.team.svn.ui.command.EditPropertiesCommand,Show Properties,
		,
		Category(org.eclipse.team.svn.ui.command.category,SVN,null,true),
		org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@51a06fd5,
		,,true),null),
	org.eclipse.ui.defaultAcceleratorConfiguration,
	org.eclipse.ui.contexts.window,,,system)
Comment 6 Peter Carlson CLA 2015-07-12 15:25:56 EDT
I wanted to add just a couple more notes:
normally I dont get past the spash screen, it stops at org.eclipse.ltk.ui.refactoring or org.eclipse.jst.j2ee.ui

Every now and then it will show the gui but hangs.  I'll get an incomplete gui (only top 1/4th of icons are shown, and even though the main container window is maximized, all of the panes, and docks are not in their correct place (they seem to be placed for a smaller window layout).  If I then click on the minimize/maximize/close buttons for the main window, it does nothing.  Worse it now seems to freeze some event loop for gnome-shell.  If I click on activities, or alt-tab, or the overview key (windows key), nothing happens.  if I type, nothing happens.  Then after killing the java process, all the events that were queued now execute (ie: windows key, type h e l p, hit esc)
Comment 7 Lars Vogel CLA 2015-07-16 00:36:15 EDT
Eclipse still works fine for me on Ubuntu 14.04. Can you try the Eclipse SDK from http://download.eclipse.org/eclipse/downloads/

The Java EE plug-ins might be causing that, I have them not installed.
Comment 8 Lars Vogel CLA 2015-08-12 12:38:42 EDT
Anything new here? Please reopen if it still does not start for you.
Comment 9 Peter Carlson CLA 2015-08-12 12:56:27 EDT
The problem has not manifested itself in a couple of weeks.  It is possible that I was suffering from a hardware issue as I replaced my mobo and memory and cpu (normal hardware upgrade) and have not had the problem even once since.

However it does reveal another very serious issue, and that is the inability to troubleshoot these types of issues.  A "debug" log that is much more instrumented showing each step of the init process.  There is a log but it seems to not be detailed enough.  The stack trace is nice, but if jstack cant attach it's of no use.