Feb 14

I downloaded Eclipse Version: Build id: M20071023-1652 and built the client’s project. Everything was fine… It was fast, stable, and there were no configuration differences between the three supportive platforms. One day I hit the shortcut key for Open Resource (Apple/Command + Shift + R ), typed in a file name, hit enter and boom… first crash. Now, every time I want to use that feature Eclipse crashes on my session. The dialog box opens, I can type a file name and hit enter but before the file opens it crashes.

Looking at the crash log in ~/Library/Logs/CrashReporter/ and they are all very similar to this:

Process: eclipse [6516]
Path: /Applications/eclipse/
Identifier: org.eclipse.eclipse
Version: 3.3 (3.3)
Code Type: X86 (Native)
Parent Process: launchd [156]

Date/Time: 2008-02-15 14:27:50.676 -0800
OS Version: Mac OS X 10.5.2 (9C31)
Report Version: 6

Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000000002ac
Crashed Thread: 0

Wondering if anyone else has seen this or knows of a fix.

The Eclipse IDE was working perfect for me on Mac OS X… Actually I always used it on Linux only because the Mac OS X version always a little weaker (from a stability perspective) and my PowerBooks were a little slower than my PCs. Now I have a 17″ 2.33GHz MacBook Pro with 2gb of ram.. and I figured I would give it shot as Eclipse has come a long way…

5 Responses to “Eclipse’s Open Resource feature causes a crash.”

  1. Ryan Says:

    I am having the same issue… Any ideas on how to work around this?

  2. Theo Says:

    I posted on this recently.

    Try downloading the latest stream stable build of eclipse.

  3. Justin Says:

    Just replace a couple of JARs in your existing 3.3 installation. See here:
    It worked great for me, with the only difference being that the JARs I extracted were v3349.

  4. Anders Says:

    Exact same problem for me!!! So annoying it just started to happen for no obvious reason… will check out those suggestions by other commentors!

  5. Kamran Kazempour Says:

    I just upgraded to Version: 3.3.2 and it works fine for me now.

Leave a Reply

You must be logged in to post a comment.