Eclipse (4.4) and other Java applications unusable under El Capitan DP3

Eclipse was working properly under Beta 1 and Beta 2, but seems to be having issues under Beta 3. The splash screen appears, and loading completes, and even shows my workspace. (Complete with projects, last-open tabs and contents, etc.)


However, the GUI thread seems completely stalled - I have the rainbow wheel of death perpetually, and cannot interact with any of the UI.


Update: I updated to Eclipse Mars (4.5) and am experiencing the same issue.

couldn't agree more.

I think Apple won't go that far to drop Java support

P.S. I'm lucky than you by only upgrade one iMac, and keep my MBP at Yosemite. but this issue is still an annoying one.

I have just installed the public El Capitan beta.

Eclipse 4.3 hangs at a later stage now, but still hangs.

Eclipse 4.4 gets to the workspace selector but freezes at that stage.


So, no real improvement to the developer beta 3.

I really needed Java/Eclipse. So, I went back to DP2. FWIW, here's how:


  1. Install the original Beta 1. It is available from your app store purchases tab.
  2. After installing, your system may not be able to find Beta 2 automatically. So, you need to follow the steps in the thread below.

    https://forums.developer.apple.com/thread/6624

    Mainly, make sure the software update is set correctly. Even with this set, my system did not detect Beta 2 automatically. So, I manually downloaded DP2 and installed it. Mail quit on starting. Simply, deleting all the mail accounts (from System Preferences -> Internet Accounts) helped.
  3. Tested it today. Looks like everything is fine. Eclipse is back to working. So, I have a DP2 with the new iTunes and Apple Music.

Did you install it like an update, or needed to do a clean install of OSX with all your data backed up, and restored after the installation?

Installed DP1 just like an update, over DP3.

I have the same problem too, and my eclipse is eclipse luna.

They did tests thats why it's mentioned in the Know Issues list!


OS X v10.11 Developer beta Release notes

Thanks Srini! Reinstalling DP2 over DP3 (DP1 from Purchases tab in App Store; DP2 update then showed up automatically) worked for me. Except for Mail.app config everything seems to work again.

Update: When going back from DP3 to DP2 Mail.app can be fixed by deleting all files starting with ~/Library/Mail/V3/MailData/Envelope Index

Same here: I try with java 7 and 8 with some Eclipse and STS (10.11 Beta (15A216g))


Eclipse

eclipse-java-mars-R-macosx-cocoa-x86_64.tar.gz

eclipse-jee-mars-R-macosx-cocoa-x86_64.tar.gz



STS

spring-tool-suite-3.6.4.RELEASE-e4.4.2-macosx-cocoa-x86_64.tar.gz

spring-tool-suite-3.7.0.RELEASE-e4.5-macosx-cocoa-x86_64.tar.gz


/System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/3.2/include/cl_kernel.h:4840:21: note: candidate function not viable: requires 3 arguments, but 4 were provided
float2 __OVERLOAD__ clamp(float2 x, float2 minval, float2 maxval);
                    ^
/System/Library/Frameworks/OpenCL.framework/Versions/A/lib/clang/3.2/include/cl_kernel.h:4839:20: note: candidate function not viable: requires 3 arguments, but 4 were provided
float __OVERLOAD__ clamp(float x, float minval, float maxval);
                   ^
Unable to compile kernel. We should debug this.

This also disabled my Eclipse. A fix would be nice.

Yes, this killed my Eclipse too, I'm running Luna, the workspace loads and I even see the editor, but then it hangs.

I got all excited about OS X El Capitan Beta Supplemental Update that fixes issues that may cause some apps to quit unexpectedly. Nope it doesn't fix Java app issues.

I used dtruss on Eclipse Mars in the El Capitan public beta to see where it might be getting stuck. It seems like it's looping trying to get the current time, and failing.



sudo dtruss -p <PID>


gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

gettimeofday(0x7FFF5FBFD2D0, 0x0, 0x100) = 1436561967 0

gettimeofday(0x7FFF5FBFDD10, 0x0, 0x100) = 1436561967 0

gettimeofday(0x7FFF5FBFCC20, 0x0, 0x100) = 1436561967 0

gettimeofday(0x7FFF5FBFE010, 0x0, 0x100) = 1436561967 0

gettimeofday(0x7FFF5FBFD2D0, 0x0, 0x100) = 1436561967 0

psynch_cvwait(0x10070D568, 0x100000100, 0x0) = -1 Err#316

psynch_cvwait(0x100644868, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x10070D568, 0x100000100, 0x0) = -1 Err#316

psynch_cvwait(0x100644868, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x100644868, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x10070D568, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x100644868, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x10070D568, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x100644868, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x10070D568, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x100644868, 0x100000100, 0x0) = -1 Err#316

psynch_cvwait(0x10070D568, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

psynch_cvwait(0x100644868, 0x100000100, 0x0) = -1 Err#316

psynch_cvwait(0x10070D568, 0x100000100, 0x0) = -1 Err#316

gettimeofday(0x700001558C90, 0x0, 0x0) = 1436561967 0

gettimeofday(0x700001D70580, 0x0, 0x0) = 1436561967 0

My log is different, failing at native UI calls. I hope the issue will be resolved on DP4, as surprising number of development tools (and CrashPlan) are broken by this bug.

There is an issue filed on the eclipse side: https://bugs.eclipse.org/bugs/show_bug.cgi?id=472259

still no solution for this problem?

I have not seen any, my solution so far has been to use Dreamweaver CS6 until the Eclipse bug is fixed. 😟

I would like to also state, that no version of Eclipse is working for me currently. Once I open it up and shows the start up screen in the square box and crashes so I have to force quit it. I wish there was a solution towards this problem. How long do you guys think it will take? Thanks

You sir, are a genius! It worked perfectly! I can now use Eclipse!

Tried the "Supplementary Update" today, still hasn't fix this... TT

come on ... Apple...


P.S. Is there 32bit eclipse for Mac? and anyone try it after updating the supplementary update of DP3 which focus on 32bit?

Same with me, I can't open it. Stuck at start screen.

This seems to be a bug with SWT applications in general.

SWT (https://www.eclipse.org/swt/) is the gui library Eclipse uses which is why Eclipse is broken but it is not exclusive to Eclipse.

I'm on the same boat. Eclipses not working after the latest patch. Please give us an ETA. Thanks.

Is there any way to download DP2 because I have no developer account yet to download this. I'm developing android application with Eclipse for my office.

Now i'm facing with a big trouble after upgrading this public beta.

Just installed El Capitan (15A215h / Public Beta 1) and experiencing the same problem with Eclipse (Mars).

Eclipse (4.4) and other Java applications unusable under El Capitan DP3
 
 
Q