Solve a problem – Filter by language, license, keyword, owner, or search text to find code & info fast. Join Siafoo Now or Learn More

Only free, if your time is.

over 9 years ago

For the past week I have been completely unable to use eclipse due to a horrible horrible nasty nasty hard crash, when I tried to open a project. The crash looked like:

[stou@cipher tools]$ ./eclipse/eclipse
*** glibc detected *** /usr/bin/java: free(): invalid pointer: 0x000000000145cdb0 ***
======= Backtrace: =========
======= Memory map: ========
00400000-00408000 r-xp 00000000 08:03 13107694  /usr/lib/jvm/java-1.6.0-openjdk-
00608000-00609000 rw-p 00008000 08:03 13107694  /usr/lib/jvm/java-1.6.0-openjdk-
00f6d000-0645b000 rw-p 00000000 00:00 0         [heap]
d8000000-db7d0000 rw-p 00000000 00:00 0
db7d0000-e8000000 rw-p 00000000 00:00 0
e8000000-e9ab0000 rw-p 00000000 00:00 0
e9ab0000-f8000000 rw-p 00000000 00:00 0
f8000000-100000000 rw-p 00000000 00:00 0
32c9800000-32c9804000 r-xp 00000000 08:03 3145814                        /lib64/libuuid.so.1.3.0
<a few pages of similar crap>

best of all the Automatic Bug Reporting Tool that comes with Fedora , and I just got used to using, was totally useless in this instance.

I was too busy with grading and other school related activities to try to get to the bottom of this crash... until today. After a 5 minute internet search I found the cause and solution to this problem. It turns out that something in KDE sets MALLOC_CHECK_=3 which catches some bug in eclipse... which somehow crashes the whole JVM. Anyway doing an unset MALLOC_CHECK_ fixed the issue.

Someone, probably an Apple/Microsoft fan boy, said... "open source is only free if your time is"...


over 9 years ago (07 Dec 2010 at 01:59 PM) by David Isaacson
In fairness, though... it was KDE's fault not eclipses'. Although I still really love (hate) the 'undo should delete that file you just worked on for 2 hours' "feature"
over 9 years ago (07 Dec 2010 at 04:30 PM) by Stou S.
It's eclipse's fault (or libSWT's fault actually) for having a free() on an invalid pointer. Also that feature you are referring to is the svn plugin's fault (i.e. subclipse)