eclipse crashed with SIGABRT in instanceKlass::oop_follow_contents()

Bug #745536 reported by Nguyen Huu Binh Minh
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eclipse (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: eclipse

Just open Eclipse, then it told me that it crashed, but it's still running.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: eclipse-platform 3.5.2-8ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
Date: Wed Mar 30 15:09:44 2011
ExecutablePath: /usr/lib/eclipse/eclipse
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/eclipse/eclipse
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: eclipse
StacktraceTop:
 instanceKlass::oop_follow_contents(oopDesc*) () from /usr/lib/jvm/java-6-openjdk/jre/bin/../lib/i386/client/libjvm.so
 MarkSweep::follow_stack() () from /usr/lib/jvm/java-6-openjdk/jre/bin/../lib/i386/client/libjvm.so
 MarkSweep::FollowRootClosure::do_oop(oopDesc**) () from /usr/lib/jvm/java-6-openjdk/jre/bin/../lib/i386/client/libjvm.so
 Universe::oops_do(OopClosure*, bool) () from /usr/lib/jvm/java-6-openjdk/jre/bin/../lib/i386/client/libjvm.so
 SharedHeap::process_strong_roots(bool, bool, SharedHeap::ScanningOption, OopClosure*, CodeBlobClosure*, OopsInGenClosure*) () from /usr/lib/jvm/java-6-openjdk/jre/bin/../lib/i386/client/libjvm.so
Title: eclipse crashed with SIGABRT in instanceKlass::oop_follow_contents()
UpgradeStatus: Upgraded to natty on 2011-03-10 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
mtime.conffile..etc.eclipse.ini: 2010-05-17T16:08:38.143600
xulrunner-versions:
 /usr/lib/xulrunner-1.9.2.16pre
 /usr/lib/xulrunner-2.0
 /usr/lib/xulrunner-2.0-addons

Revision history for this message
Nguyen Huu Binh Minh (nguyen-huu-binh-minh) wrote :
Revision history for this message
Benjamin Schmid (benbuntu) wrote :

This seems to be a bug in the JVM Implementation. To be more precise the memory management (GC) part of it.
See i.e. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6896739

I stumbled over this isse because we have the same failures, but only with very large Java Heap Sizes. Do you set large Heap Size for Eclipse or have you a machine with very large memory.

Maybe try to limit the Heap to sth. like 1GB with -Xmx1024M.
Refer to http://wiki.eclipse.org/FAQ_How_do_I_increase_the_heap_size_available_to_Eclipse%3F on how to achieve this.

Revision history for this message
dino99 (9d9) wrote :

This version has expired long ago; no more supported

Changed in eclipse (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.