I'm currently using the Eclipse Indigo 3.7 IDE for Java Developers.So today I tried to update it to the latest 3.7.1 but during the update process a error downloading0 with Comparison method violates its general contract! pops out and the whole update process stucks at that process. Can someone help me with this problem?
I'm using both JDK 7x64 and JRE 7x64
Due to lack of information, I can suggest it's related to eclipse bug 317785, if you are using Java 1.7.
Possible workarounds:
* use JRE6
OR
* when using JRE7, theres a small rarely documented feature
set system property java.util.Arrays.useLegacyMergeSort=true
This should use old implementation and should not bring up the bug
I was able to fix this problem by using this workaround taken from the link suggested by 4e6 and VonC (bugs.eclipse.org/bugs/show_bug.cgi?id=317785):
To clarify comment #22 for those on JRE7 who can't upgrade to 3.7.1
because of this bug:
Add the following line to your eclipse.ini:
-Djava.util.Arrays.useLegacyMergeSort=true Then run the update to 3.7.1 from inside Eclipse again, it should succeed now. Afterwards, you should be able to drop that line from eclipse.ini again.
Related
My application isn't running correctly with Java 9. In order to debug it, I upgraded to Eclipse 4.7 (oxygen) since Neon doesn't have Java 9 support, and applied the Java 9 support patch.
After doing so, eclipse was failing to load any of my pre-existing Java Applications. Thinking it might be a version difference thing, I deleted them, to try re-adding. But when I click the "New" button to add a configuration, nothing happens.
If I double-click "Java Application," I get the following error:
An error has occurred. See error log for more details.
tried to access method org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.getTabViewer()Lorg/eclipse/debug/internal/ui/launchConfigurations/LaunchConfigurationTabGroupViewer; from class org.eclipse.jdt.internal.debug.ui.launcher.LocalJavaApplicationTabGroup
I am able to add configurations for other types of applications (Java Applet, Eclipse Application) so it seems only to be an issue with Java Applications.
I also tried a fresh workspace, but that has the same issue. How can I fix this?
This is kind of a duplicate but since I experienced the issue and have seen a few others post about it, I'll post my answer of how I fixed it here.
If you go here: https://marketplace.eclipse.org/content/java-9-support-beta-oxygen/
You need to follow the step about updating Eclipse 4.7 from the link that ends in 4.7-U-builds. When you go to Install New Software and select Eclipse SDK, click Next until you get to the Install Remediation Page, and make sure that you are selecting the second option that says something like "update my installation to be compatible with the items being installed" instead of the option that says "keep my installation the same and modify the items being installed to be compatible."
The first time I installed Java 9 updates, I did it the latter way and ran into this problem. Now that I've gone back and chosen the former, I am able to add Java Application Run Configurations again.
Hope this helps.
Eclipse Oxygen.1a (4.7.1a) Release
Update as of 11 October,2017 - You shall upgrade to the latest eclipse package Eclipse Oxygen.1a (4.7.1a) which is marked as released and supports Java 9.
I have Eclipse Juno with Java EE, PHP, C++ and PyDev in it and it was working perfectly under Ubuntu 12.04 and later under 14.04.
Yet, when I upgraded my OS to Ubuntu 14.10, Eclipse doesn't work anymore, whenever I try to open it, it shuts down immediately.
I want to upgrade it to Luna but it doesn't give me the chance to launch the upgrade, I have an idea I have and wish to hear your advice on whether it is right or wrong.
What I'd like to do is to download Luna and extract it over the older version.
Will this work? Or will it make it even worse?
Is there anyone who tired it before?
You may even download Luna, and extract it to a different folder (not necessary on top of the older version).
Afterwards, launch Luna and try to load your previous workspace(s). You might want to backup your workspaces folder, before letting Luna attempt and load from there.
Updating the eclipse through the command line is safer. Try it using eclipse site
and also refer to this answer
I find solution here https://bugs.eclipse.org/bugs/show_bug.cgi?id=440660#c20 on comment 20
This seems to be a bug in GTK according to https://bugs.launchpad.net/ubuntu/+source/gtk2-engines-oxygen/+bug/1242801
(there a similar problem for Meld was reported).
Another workaround mentioned there is
For oxygen, edit the normally already existing file "/usr/share/themes/oxygen-gtk/gtk-2.0/gtkrc" and change
GtkComboBox::appears-as-list = 1
into
GtkComboBox::appears-as-list = 0
This workaround is working for me.
I have been running eclipse properly. After it loads I get:
"Initializing Java Tooling".
Incompatible magic value 0 in class file org/eclipse/jdt/internal/core/search/BasicSearchEngine
I have been looking, and what I have found is Eclipse hanging initializing java tooling
I have set JAVA_HOME and -vm in eclipse.ini
Still, no success.
Any ideas would be appreciated
=======
Added after I solved the issue
(Stack Overflow won't let me post this as an answer cause I am of ill repute.)
Never mind.
It may be important to have the answer to what I did so that people that have the same issue does not have to go through the hoops I went.
First, I went to the Help/About Eclipse/Installation Details. In the Installation History, with using compare and revert, I started reverting what I had installed (Compare and Revert are pretty cool BTW.) I finally detected which was the latest stable version, and the installation that broke it all
Spring Source at http://dist.springsource.com/release/TOOLS/update/e3.7
Initially I selected some extra components that sounded cool, but the second time around I pretty much went for the required, plus support for AOP, Web Tools, and Flex and WebServices. Other than that I ignored all the rest of the stuff. That worked.
I had selected before (one of the ones that killed it, do not exactly which one), in addition to what I left installed: Spring Mylyn Integration Spring Tool Suite AWS Integration Spring Tool Suite Maven Support Eclipse Weaving Source
I also had the "Mylyn Builds Connector: Jenkins/Hudson integration", which had worked for me in the past. I still suspect that it was one of the Spring components.
I hope this helps
Usually, a restart will solve this issue. As #Carsten mentioned, close all open files and terminate eclipse then re-launch the application. I have encountered this problem many times. The causes of this range from:
Low memory assigned to eclipse. You could increase the memory by editing the eclipse.ini file and change the options -X* JAVA_OPTS
Loading large files (XML is always a culprit in this case).
Attempting to format large XML files
Immediately after installing a new plugin and not restarting eclipse right away
etc
Clean \Workspaces\MyEclipse 8.5 M2.metadata.plugins\org.eclipse.core.resources.projects folder after closing eclipse/myeclipse .That's it.
This is an STS issue however they blame it on an Eclipse bug which has been fixed:
https://issuetracker.springsource.com/browse/STS-696. If you look at the dependencies of the STS plugin you will notice that the Eclipse WTP version is way passed the one that is mentioned in the Eclipse Bug..
I have just seen that new major release (3.6 Helios) of eclipse is available for download. I want to try it, but before that I want to know if anybody experienced any major problems.
I want to determine If I could try this or not, since my project setup is complex and easily takes 2, 3 hours normally; I don't want to take any risk.
No major issue sp far.
The main problems I have seen are platform specific, like this crash in Ubuntu.
Small differences are noted in this blog post.
As usual, I always prefer a full Eclipse installation beside the ones I already have.
And for major update, I like to recreate a workspace dedicated for that release, just to be on the safe side.
That way, my old Eclipse release still has its own workspace fully functional.
I also test the plugins in both version by using a shared dropins folder.
Yes i experienced a major problem with helios, but only in WTP context. If you work with WTP you should immediately update to WTP-M-3.2.1. This should fix the issue of taking up to a minute for hot deployment (re-publishing to the server). The eclipse bug issue.
The most disturbing thing for me was the way j2ee projects are configured: there is no more j2ee dependencies, and it is not obvious at the first glance to see you have to use resource assembly (but it does not resist a few minutes searching the web).
Apart for that, I had no real issue in updating: everything went smooth, and plugins I use work well under helios.
Nothing so major, but some suggestion features are a bit buggy:
sometimes instead of suggesting to create a method, it suggest a cast, and inserts a cast to Object
when there are interfaces methods with generics, some of them are added as unimplemented even though they exist in the parent class.
These are two things I encountered for the past week.
On Windows, Helios does appears to have a pretty critical conflict with the latest oracle JDK patch (JDK 1.6 update 21):
https://bugs.eclipse.org/bugs/show_bug.cgi?id=319514
Any version before that is ok.
There is an issue with Helios and Oracle JVM 1.6.0 update 21. Eclipse launcher sets permgen size using Sun-jvm-specific command line option, but Oracle changed vendor string from "Sun Microsystems" to "Oracle", and Eclipse now fails to detect Sun-JVM, so it is not setting right permgen size. Quick solution is to set permgen by yourself in eclipse.ini.
I'm getting incredibly slow autocomplete. The bug , with a workaround, is here https://bugs.eclipse.org/bugs/show_bug.cgi?id=317979
We switch to 64bits Helios under Windows 7 recently. We saw a major improvement in memory management no more Out Of Memory errors inside Eclipse. Much better performances as well. But we have a big issue with SVN and SVN Kit plugins they are constantly displaying Malformed Network data errors or Handshake fail errors when synchronising with our repository under svn+ssh. Was perfectly running under 32 bits Indigo or Galileo.
Since adding the Blackberry Java classes from their website into eclipse, I've had it where eclipse will randomly close, with no discernible pattern, rhyme, error or reason. Here is the environment/software packages that I am using:
Windows XP SP2
Eclipse v3.5.1
Blackberry Java Plugin v1.1.1.200911111641-15
Blackberry Java SDK 4.5.0.21
I've tried the usual steps of complete uninstall and reinstallation of Eclipse and the accompanying plugins on multiple systems with the same configuration, including one that had a fresh install of Windows XP SP2. Upgrading to Eclipse 3.6 didn't work (the plugin wont' install as it's the wrong version), nor the downgrade to 3.4 for the same reason. I also increased the heap size to 512 (system has two gigs of memory) as some research into Eclipse doing this type of thing with Groovy was resolved that way, but again, no dice. Eclipse works great when the blackberry plugins are not installed, and no entries of errors or issues in the event log are helping to show what the issue with these plug-ins might be.
So if anyone has ran into this issue, and even better, has a solution, I'd love to hear about it. Thanks in advance.
EDIT: An additional to my issue, autoComplete with the Blackberry SDK seems to make this extremely unstable, like almost a guaranteed crash. Is this fixable at all?
For anyone that loads this question up trying to find a solution, I've never found a fix. It seems to be a bug with this version of the IDE. If there is a fix, please post.
Did you try to downgrade Eclipse to 3.4 (Ganymede)? I experienced similar issues when I tried upgrading Eclipse to something greater than 3.4.2.
I think the problem is with the plugin, not the IDE. Eclipse has always been stable for me until I installed the BB plugin. Since then it crashes all the time. Since I've installed the release (non-beta) version of the plugin that was recently released I can't even get my project to build.
This could be a manifestation of this bug in Eclipse. Check your C:\eclipse directory for files like hs_err_pidxxxx.log. The file goes on to explain this error:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x753ba053, pid=3144, tid=5820
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Client VM (16.3-b01 mixed mode, sharing windows-x86 )
# Problematic frame:
# C [USP10.dll+0x1a053]
I've been experiencing this as well. It's completely debilitating. It causes Eclipse to just up and crash out of nowhere (and programming in a language as verbose as Java without Content-Assist is insane).
The bug has been fixed in Eclipse 3.6M7, but unfortunately I can't get the JDE Plug-in to install in the latest release candidate.
This is a known issue with Eclipse 3.5.X and has been fixed for 3.6.0
Bug Ticket link on Eclipse Bugzilla: https://bugs.eclipse.org/bugs/show_bug.cgi?id=283503
Looks like we are stuck with this until the next update to the BB Eclipse plugin.