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

Bug 90868

Summary: Eclipse crashes often if not always, CVS repositories used
Product: [Eclipse Project] Platform Reporter: Sensei <senseiwa>
Component: SWTAssignee: Billy Biggs <billy.biggs>
Status: RESOLVED DUPLICATE QA Contact:
Severity: blocker    
Priority: P3 CC: billy.biggs
Version: 3.0.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux-GTK   
Whiteboard:

Description Sensei CLA 2005-04-08 17:43:33 EDT
I tried for 11 times to checkout a remote ssh-based cvs repository, and each
time eclipse crashed reaching the 40% of checkout.

At the 11th time, it succeeded, I couldn't figure out why.

Now, I'm doing simple tasks, trying to build a Qt application, without
succeeding because it's a 5/6 probability of crashes. Note that the crash occurs
randomly at eclipse boot, or selecting a component from the UI, mainly randomly.

I'd be glad to help, but I don't know what to do to give you sufficient
informations.

The debugging information I can give right now are those:

sensei@quantum:projects> /home/sensei/bin/eclipse/eclipse
#
# HotSpot Virtual Machine Error, Internal Error
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode)
#
# Error ID: 43113F32554E54494D45110E4350500308
#
# Problematic Thread: prio=1 tid=0x08681d40 nid=0x1b0e runnable
#

Heap at VM Abort:
Heap
 def new generation   total 576K, used 575K [0xaba40000, 0xabae0000, 0xabf20000)
  eden space 512K,  99% used [0xaba40000, 0xababffd8, 0xabac0000)
  from space 64K, 100% used [0xabac0000, 0xabad0000, 0xabad0000)
  to   space 64K,   0% used [0xabad0000, 0xabad0000, 0xabae0000)
 tenured generation   total 7184K, used 6046K [0xabf20000, 0xac624000, 0xafa40000)
   the space 7184K,  84% used [0xabf20000, 0xac507a30, 0xac507c00, 0xac624000)
 compacting perm gen  total 14080K, used 14065K [0xafa40000, 0xb0800000, 0xb3a40000)
   the space 14080K,  99% used [0xafa40000, 0xb07fc658, 0xb07fc800, 0xb0800000)
sensei@quantum:projects>

The crash window tells me:

JVM terminated. Exit code=1
/usr/bin/java
-cp /home/sensei/bin/eclipse/startup.jar org.eclipse.core.launcher.Main
-os linux
-ws gtk
-arch x86
-showsplash /home/sensei/bin/eclipse/eclipse -showsplash 600
-exitdata /home/sensei/bin/eclipse/eclipse -exitdata 3a78001
-vm /usr/bin/java
-vmargs
-cp /home/sensei/bin/eclipse/startup.jar org.eclipse.core.launcher.Main

It's not a matter of free memory:

sensei@quantum:projects> free
             total       used       free     shared    buffers     cached
Mem:       1555372     756020     799352          0      33388     348404
-/+ buffers/cache:     374228    1181144
Swap:       917272          0     917272
sensei@quantum:projects>
Comment 1 Billy Biggs CLA 2005-04-08 18:10:04 EDT
Is there a file in your home directory or the eclipse install called
hs_err_pidXXXX.log?  This will hopefully have the full crash dump.

Useful information:
  Linux distribution, GTK+ version, GTK+ theme used (is it gtk-qt based?)
Comment 2 Sensei CLA 2005-04-08 23:50:33 EDT
Unfortunately, no logs (it's the first thing I've done before posting the bug):

sensei@quantum:~> find . -name "*.log"
sensei@quantum:~>

I'm using eclipse under SuSE 9.2pro, Eclipse vanilla, not suse's rpms.

GTK+ 2.4.9 (suse rpm: gtk2-*-2.4.9-10)
Java 1.4.2 (suse rpm: java-1_4_2-sun*-1.4.2.06-1.1)
GTK/QT 0.5 (suse rpm: gtk-qt-engine-0.5-9.2)

No Gnome/GTK theme has been selected, as I don't use gnome (I develop only pure
Qt). 
Comment 3 Billy Biggs CLA 2005-04-08 23:52:14 EDT
OK, if you're running under KDE on SuSE 9.2 you are likely using the gtk-qt
theme engine.  Please check for an update from SuSE for this RPM, as it is known
to cause crashes in Eclipse, often when using the CVS repositories perspective.
 This is due to a (fixed) bug in the theme engine relating to tiny scroll bars.
Comment 4 Billy Biggs CLA 2005-04-08 23:53:42 EDT
If that fixes it, I will mark this as a duplicate of bug 77928.  Your crash dump
has me worried though, since it points to a VM internal error rather than just a
crash as I would have expected.
Comment 5 Sensei CLA 2005-04-09 00:22:53 EDT
Removed the gtk-qt-engine, seems to work. I suggest expanding the bug repository
with a gtk-qt interaction as not recommended, possible crashes. Anyway, I will
do more tests in the next days.

Just for a test, I have version gtk-qt-engine 0.5-9.2, the available package is
0.5-9. I downgraded it to the *previous* version, but nothing had affected the bug:

Now at least I get a stderr:

sensei@quantum:~> /home/sensei/bin/eclipse/eclipse
QPixmap: Invalid pixmap parametersQPainter::begin: Cannot paint null pixmap
QPainter::setPen: Will be reset by begin()
QPainter::setBrush: Will be reset by begin()
QPainter::setBrush: Will be reset by begin()
QPainter::setPen: Will be reset by begin()
QPainter::setPen: Will be reset by begin()
[...]
An unexpected exception has been detected in native code outside the VM.
Unexpected Signal : 11 occurred at PC=0x4118F172
Function=XSetTile+0x12
Library=/usr/X11R6/lib/libX11.so.6

Current Java thread:
        at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(Native Method)
        - locked <0xafddc300> (a java.lang.Class)
        at org.eclipse.swt.widgets.Display.eventProc(Display.java:879)
        at org.eclipse.swt.internal.gtk.OS.gtk_adjustment_value_changed(Native
Method)
        - locked <0xafddc300> (a java.lang.Class)
        at org.eclipse.swt.widgets.ScrollBar.setValues(ScrollBar.java:653)
        at org.eclipse.swt.custom.StyledText.setScrollBars(StyledText.java:7022)
        at org.eclipse.swt.custom.StyledText.handleResize(StyledText.java:5116)
        at org.eclipse.swt.custom.StyledText$7.handleEvent(StyledText.java:4753)
[...]
Dynamic libraries:
08048000-08056000 r-xp 00000000 03:03 576985    
/usr/lib/jvm/java-1.4.2-sun-1.4.2.06/jre/bin/java
08056000-08059000 rwxp 0000d000 03:03 576985    
/usr/lib/jvm/java-1.4.2-sun-1.4.2.06/jre/bin/java
41000000-41016000 r-xp 00000000 03:03 611587     /lib/ld-2.3.3.so
41016000-41018000 rwxp 00015000 03:03 611587     /lib/ld-2.3.3.so
4101a000-41129000 r-xp 00000000 03:03 611588     /lib/tls/libc.so.6
41129000-4112a000 ---p 0010f000 03:03 611588     /lib/tls/libc.so.6
4112a000-4112b000 r-xp 0010f000 03:03 611588     /lib/tls/libc.so.6
[...]
b7bb5000-b7fb1000 r-xp 00000000 03:03 577103    
/usr/lib/jvm/java-1.4.2-sun-1.4.2.06/jre/lib/i386/client/libjvm.so
b7fb1000-b7fcd000 rwxp 003fb000 03:03 577103    
/usr/lib/jvm/java-1.4.2-sun-1.4.2.06/jre/lib/i386/client/libjvm.so

Heap at VM Abort:
Heap
 def new generation   total 576K, used 361K [0xaba40000, 0xabae0000, 0xabf20000)
  eden space 512K,  63% used [0xaba40000, 0xaba917c0, 0xabac0000)
  from space 64K,  55% used [0xabac0000, 0xabac8f38, 0xabad0000)
  to   space 64K,   0% used [0xabad0000, 0xabad0000, 0xabae0000)
 tenured generation   total 6944K, used 6774K [0xabf20000, 0xac5e8000, 0xafa40000)
   the space 6944K,  97% used [0xabf20000, 0xac5bda08, 0xac5bdc00, 0xac5e8000)
 compacting perm gen  total 14592K, used 14390K [0xafa40000, 0xb0880000, 0xb3a40000)
   the space 14592K,  98% used [0xafa40000, 0xb084da78, 0xb084dc00, 0xb0880000)

Local Time = Fri Apr  8 23:09:59 2005
Elapsed Time = 17
#
# The exception above was detected in native code outside the VM
#
# Java VM: Java HotSpot(TM) Client VM (1.4.2_06-b03 mixed mode)
#
# An error report file has been saved as hs_err_pid19883.log.
# Please refer to the file for further information.
#

Crash window reports:

JVM terminated. Exit code=1
/usr/bin/java
-cp /home/sensei/bin/eclipse/startup.jar org.eclipse.core.launcher.Main
-os linux
-ws gtk
-arch x86
-showsplash /home/sensei/bin/eclipse/eclipse -showsplash 600
-exitdata /home/sensei/bin/eclipse/eclipse -exitdata 9bf8007
-vm /usr/bin/java
-vmargs
-cp /home/sensei/bin/eclipse/startup.jar org.eclipse.core.launcher.Main
Comment 6 Billy Biggs CLA 2005-04-11 09:59:43 EDT
That crash log is the same as bug 77928 which AFAIK was confirmed to be a bug in
gtk-qt.  Can you find out if 0.5-9.2 is the latest from SuSE?
Comment 7 Billy Biggs CLA 2005-04-14 11:20:15 EDT
I am going to mark this as a duplicate of 77928 since this is the same problem.
 We should report the answers there.

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