Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 360776

Summary: Crash in __float128+0x20 when selecting a workspace at startup
Product: [Eclipse Project] Platform Reporter: Aaron Digulla <digulla>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: arunkumar.thondapu, bruno82, eclipse.felipe, eclipse, grant_gayed, jal, kdevolder, Silenio_Quarti, Sroka.Steven
Version: 3.7.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:
Attachments:
Description Flags
Java dump
none
Error Log
none
Error Log
none
JDK crash log
none
JDK crash log
none
JDK 1.6.0_32 64bit crash log none

Description Aaron Digulla CLA 2011-10-13 04:26:47 EDT
Created attachment 205100 [details]
Java dump

I'm now seeing a similar problem with Indigo using Ubuntu 11.04 with glib2.0 2.28.6-0ubuntu1. My stack looks slightly different, though:


#  SIGSEGV (0xb) at pc=0x00007ff60ba8d260, pid=4922, tid=140694904461056
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libgobject-2.0.so.0+0x17260]  __float128+0x20
...

Stack: [0x00007ff615bd5000,0x00007ff615cd6000],  sp=0x00007ff615cd2960,  free space=1014k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [libgobject-2.0.so.0+0x17260]  __float128+0x20

Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  org.eclipse.swt.internal.gtk.OS._g_object_get_qdata(JI)J+0
j  org.eclipse.swt.internal.gtk.OS.g_object_get_qdata(JI)J+9
j  org.eclipse.swt.widgets.Display.removeWidget(J)Lorg/eclipse/swt/widgets/Widget;+19
j  org.eclipse.swt.widgets.Combo.deregister()V+21
j  org.eclipse.swt.widgets.Widget.releaseWidget()V+1

This always happens (tried five times). Exact steps to reproduce:

- Download and unpack eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz (MD5: 480db51fb93dc1d39ba406415bb0f966)
- Run eclipse/eclipse
- Browse to select a different workspace 
- Select "Use this as default"
- Click OK

It doesn't happen when you click "OK" without selecting a different path or when you type in the path manually. Somehow opening the file dialog triggers the bug.
Comment 1 Aaron Digulla CLA 2011-10-13 04:27:09 EDT
Might be related to bug 353144
Comment 2 Aaron Digulla CLA 2011-11-03 04:22:22 EDT
Same bug when exporting a Target Definition: As soon as I use the "Browse" button, Eclipse crashes.

This is a stable bug, happens every time.
Comment 3 Steven Sroka CLA 2012-01-12 21:09:13 EST
I notice this happens everytime I choose a workspace location at startup that is not the default.
Comment 4 Steven Sroka CLA 2012-01-12 21:09:49 EST
Created attachment 209423 [details]
Error Log
Comment 5 Steven Sroka CLA 2012-01-12 21:10:02 EST
Created attachment 209424 [details]
Error Log
Comment 6 Felipe Heidrich CLA 2012-01-13 13:35:45 EST
(In reply to comment #2)
> Same bug when exporting a Target Definition: As soon as I use the "Browse"
> button, Eclipse crashes.
> 
> This is a stable bug, happens every time.

Arun, can you please try this scenario ? Thank you
Comment 7 Bruno Mendola CLA 2012-01-30 11:31:55 EST
This happens to mee too.

Eclipse 3.7.1 under Kubuntu Linux 11.10 x86_64 w/ Sun JDK 1.6.0-26.

I think this is the same bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=335086
Comment 8 Frits Jalvingh CLA 2012-03-01 09:35:00 EST
Also crashes here quite often, and not just after closing the "select workspace" file dialog.

Using Eclipse 3.7.2 (20120216-1857) and Ubuntu 11.10 x64 using JDK 1.6.0_30.
I'll add the crash logs for those that might be interested.
Comment 9 Frits Jalvingh CLA 2012-03-01 09:36:23 EST
Created attachment 211882 [details]
JDK crash log
Comment 10 Frits Jalvingh CLA 2012-03-01 09:36:49 EST
Created attachment 211883 [details]
JDK crash log
Comment 11 Kris De Volder CLA 2012-06-04 12:13:12 EDT
Here is what seems to be another report of a crash with a very similar stack trace.

https://issuetracker.springsource.com/browse/STS-2679

This problem was reported by an STS user using a version of STS based on Eclipse 3.7 and 64 bit Kubtunt 11.10. Interestingly he's using OpenJDK instead of Sun JVM which seems to be what all the other reports in this bug where using.
Comment 12 Jörg von Frantzius CLA 2012-07-02 08:55:49 EDT
Created attachment 218154 [details]
JDK 1.6.0_32 64bit crash log

Happened with Juno release on 64bit Sun Java JVM, Build id: 20120614-1722. 

From the other comments it seems that this only happens on 64bit? Or is this only per chance, and the crash has also happened with 32 bit?

In my case, the crash happens during an "Import from existing Maven project" with m2e.
Comment 13 Silenio Quarti CLA 2012-08-31 13:02:46 EDT
Please the next 4.3 integration build. It should be fixed.

*** This bug has been marked as a duplicate of bug 383189 ***