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. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/745536 Title: eclipse crashed with SIGABRT in instanceKlass::oop_follow_contents() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse/+bug/745536/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
