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.
How to install EI Capitan public beta to OS X EI Capitan DP2.
My eclipse can't use still now. I need to use this for my work.
Please help me for this issue!
You can't. The public beta 1 is (nearly) the same as the developer beta 3 and without a developer account, you won't receive the possibility to install the developer beta.
FWIW, I've been, like many others, blocked by this issue. I've not made Eclipse work, but needed a quick workaround to keep compiling and testing.
Switched to SublimeText as a Editor and created a small Makefile quick and dirty that allows me to make my project and deploy it to tomcat.
Feel free to use it:
Same issue here.
More information in the eclipse bug tracking:
hm - not sure it will work for everyone - if you just stepped in directly to 10.11b3, you won't have b2 in your purchases tab. or is there any way to get b1?
I too am having the same issue. I don't have backup in the time machine. Is there anyway I can roll back to 10.10 Yosemite.
My entire work on the Eclipse is getting stalled
Unfortunatelly not. If you don't have any time machine backup, you won't be able to revert back to previous state. Do workspaces backup and reinstall your machine to Yosemite or wait for Apple to deliver newer beta with this issue fixed.
This is exactly my experience. After udating El Capitain Beta, Eclipse refused to start.
The farest point I got was the Workspace selection.
Most times Eclipse (Keppler/Mars) is stuck on the start screen.
I tried to reinstall Java but got the same results.
Then I tried to start from the terminal and get a long list of "candidate function" notes and at last the "Unable to compile kernel" Message.
I've tried to figure out where Eclipse uses openCL and perhaps to disable it but didn't find any easy to set parameter.
Perhaps the native SWT - Part uses openCL.
I'm relativly familiar with the Java portion of SWT but I don't know how the JNI - part is done.
I'm hoping that Apple will release a middle update to fix this: many developers application can't start with latest DP3 😟
Same for me, using the first public beta and Eclipse Luna.
If anyone finds a solution, please let us know!
Given this version of Mac OS X is beta, it probably isn't something one should be using if it is their only machine.
I too have experienced this problem and because I need to work, I'm just running Eclipse inside of a VM using the Workspace on my Mac side (via the Z: drive which is mapped to the Home directory on my Mac).
Not really sure if it is an OS X problem per se or a Java compatibilty problem that was caused by changes to the Mac OS X operating system.
There's a workaround, but corresponding comment is under review and not being released. Trying again: search for javamake on github - like github slash mnott slash javamake. I wrote a small makefile that you can adapt and that allows me to continue working, with a different editor.
Anybody have solution now?
Or anybody know the schedule of beta4?
I'm experiencing this too.
For reference, this is the URL for the bug report in the Eclipse project: https://bugs.eclipse.org/bugs/show_bug.cgi?id=472259
I solved this by installing OS X Yosemite on VMWare Fusion - I have a whole Virtual Machine just for Eclipse :/
Steps:
The installer will be downloaded into /Applications
Just a quick side-note here, from my latest digging, it seems to be anything SWT related - which is, of course, Eclipse is.
Here is a link to a thread in the Eclipse forum for this issue:
https://www.eclipse.org/forums/index.php?t=msg&th=1068258&goto=1701239&
Thanks for sharing a post with the java make files! I'm no expert in Java, I rarely use eclipse.. But I noticed a process called MRTAgent was crashing everytime I turned on my computer. This is the best article I could find on what it is: http://www.cnet.com/news/a-look-at-apples-flashback-removal-tool/
It's a malware removal tool, but it was crashing everytime I turned on my computer (only after downloading the latest java6 from apple). So I explored the file system to remove it, and I learned a lot about where Java is located (& where it's not). Two questions I have are:
1) Are there permission issues with rootless that are sandboxing tools like eclipse (simlar to what was dicussed at WWDC)?
2) Has the internal file structure changed in /Systems/Library & /Library?
JAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.8.0_25.jdk/Contents/HomeThis seems be fine. I don't know what 'Home' is, but I saw it throughout the /System/Library & /Library in places I wasn't expecting (maybe that's normal?).
Then TOMCAT is referenced which could be an issue.. and then this:
#
# Content that is to be deployed to WEB-INF/classes,
# relative to the project root of the project. More
# than one location to be separated by spaces.
#
TO_CLASSES=config/dev/ data/
#
# Content that is to be copied to WEB-INF/lib,
# relative to the project root of the project. More
# than one location to be separated by spaces.
#
TO_LIB=lib/gson-2.3.1.jar lib/log4j.jar lib/mysql-connector-java-5.1.7-bin.jar lib/ngdbc.jar lib/sap/jar
#
# Classpath. This is what we need to complie the web application's
# class files. It is not necessarily identical with what we need
# to deploy into WEB-INF/lib: It is what we need to compile.
#
CLASSPATH=../$$WEBROOT/WEB-INF/classes:../lib/gson-2.3.1.jar:../lib/log4j.jar:lib/mysql-connector-java-5.1.7-bin.jar:../lib/ngdbc.jar:../lib/servlet-api.jar- Are these paths correct in beta 3? (or the of other paths here I didn't quote above)
- Has rootless increased security to sandbox apps in ways that weren't present in previous betas?
I think it's possible to build eclipse with awareness of what it's doing, and where eclipse is doing it. Maybe change some VAR's / paths in the makefile associated with building it - flags - etc too. It may be possible ot copy some Java runtime dependencies into different folders, if eclipse has the wrong paths, and potentially building some folders prior to downloading eclipse if you know where eclipse intends to download them.
Either way, it seems like quite a manual process, and I'd rather use beta 1,2 or wait for beta 4 - it's going to change again in a week or two - I suspect they were modifying folders in /Library - /System/Library or something like that - it broke java - and it wasn't a high enough priorty to fix it before the beta was released. But after looking through it all - I'm confidident it can be fixed (and probably already has internally).
JDK 1.8.0 Update 51 which was released today does not seem to help this problem either.
This does seem to be the source of the loop!
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x11C611468, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x11C611468, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x11C611468, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x11C611468, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x11C611468, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x11C611468, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5D08, 0x0, 0x0) = 1437063218 0
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
gettimeofday(0x7FFF5FBFD240, 0x0, 0x0) = 1437063218 0
gettimeofday(0x7FFF5FBFDEC0, 0x0, 0x0) = 1437063218 0
gettimeofday(0x7FFF5FBFCDD0, 0x0, 0x0) = 1437063218 0
gettimeofday(0x7FFF5FBFDF70, 0x0, 0x0) = 1437063218 0
gettimeofday(0x7FFF5FBFD240, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x11C611468, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x700001CED580, 0x0, 0x0) = 1437063218 0
psynch_cvwait(0x100680268, 0x100000100, 0x0) = -1 Err#316
gettimeofday(0x7000014D5C90, 0x0, 0x0) = 1437063218 0
Also having this issue. Eclipse MARS with JDK 1.8 hangs at workspace selection.
OS X Build: 15A215h (Public Beta 1)
Java for OS X 2015-001 beta installs the legacy Java 6 runtime for OS X 10.11 El Capitan.
Fixed my problems.
https://support.apple.com/kb/DL1824?viewlocale=en_US&locale=en_US
Will.
I suggested the same thing one week ago (see higher up this thread) but it didn't seem to be enough to fix the problem on it's own. What did you do in addtion to that?
Did not do any addition steps. Just rebooted and it worked.
Will.