eclipse crashed with SIGABRT in instanceKlass::oop_follow_contents()
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
ProcVersionSign
Uname: Linux 2.6.38-
Architecture: i386
Date: Wed Mar 30 15:09:44 2011
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: /usr/lib/
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: eclipse
StacktraceTop:
instanceKlass:
MarkSweep:
MarkSweep:
Universe:
SharedHeap:
Title: eclipse crashed with SIGABRT in instanceKlass:
UpgradeStatus: Upgraded to natty on 2011-03-10 (19 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
mtime.conffile.
xulrunner-versions:
/usr/lib/
/usr/lib/
/usr/lib/
This seems to be a bug in the JVM Implementation. To be more precise the memory management (GC) part of it. bugs.sun. com/bugdatabase /view_bug. do?bug_ id=6896739
See i.e. http://
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. wiki.eclipse. org/FAQ_ How_do_ I_increase_ the_heap_ size_available_ to_Eclipse% 3F on how to achieve this.
Refer to http://