eclipse (3.5 & 3.6) crashes in ubuntu - java

i have a problem with eclipse within ubuntu 10.04 (x86). i installed eclipse by downloading the zip-file, not from the sources. everything worked just fine until i decided to try eclipse 3.6 which i downloaded just as i did with 3.5...
well i saved 3.6 in another directory than 3.5, started it and opened a workspace that i created with 3.5. after working a bit with 3.6 i notices the following problem:
at some times, when i type sth like CLASSNAME. or VARIABLE. (that is when the code-completion dialog pops up), eclipse crashes, when i try to
close the code completion window (e.g. by pressing ESC)
select sth from the code completion window
or anything else. this problem did NOT occur within 3.5 at ANY time. well - switching back to the old 3.5 did not solve the problem. the crashes now happened also in this version :(
so i tried to:
delete the /home/USER/.eclipse dir
reinstall java from the sources
create a completely new workspace
tried the eclipse version from sources (3.5)
nothing helped :(
i'm out of ideas... how do i get rid of this problem?

It looks like bug 308731, which is XulRunner related.
I confirm that the Steffen's solution works for me and it is necessary to set
the property "-Dorg.eclipse.swt.browser.XULRunnerPath".
I set:
-vmargs
-Dorg.eclipse.swt.browser.XULRunnerPath=/usr/bin/xulrunner-1.9.2
in my eclipse.ini
(crash when pressing Enter on content assist selection)

Add -Dorg.eclipse.swt.browser.DefaultType=mozilla at the end of your eclipse.ini file
It works for me :)

Related

Eclipse installer not showing any packages

When trying to install eclipse, when I run the installer I just get a blank box with no packages to select. Image Link
Any idea on how I could fix it, I have my java environment variable and java_home both set to the \bin location for both my java installations. The versions of java I currently am using are jdk 8 and I got jdk 16 to see if that might fix the issue but it didn't. As well, there weren't any errors or anything it just shows the empty box and shows that there's an update but I'm not sure what it's trying to update. Any idea how I could fix it?
Solution that worked for me:
Ok so after some fiddling around I had to search "eclipse" in the search all bar in windows. Then after some scrolling I was able to find the file "eclipse-isnt.exe" and after running that it showed the stuff to download and solved my problem. The "eclipse-isnt.exe" ended up being located in "C:/Users/(user)/AppData/Local/Temp/(random temp file)/eclipse-inst.exe".
Hope this helps out
Also running the file as administrator worked

Eclipse doesn't start in Ubuntu 14.04

I have a problem trying to launch Eclipse in Ubuntu 14.04. Splash picture pops up, then blinks, turns white - and nothing happens until kingdom come.
I have tried Luna, Kepler and 3.8 (from Ubuntu repository). EE and SE editions - both the same. I have also tried to launch them with different (oracle) vm - 1.7 and 1.8.
And yes, I have tried the -clean and simple workspace removal.
This is the only thing it says in console:
org.eclipse.m2e.logback.configuration: The
org.eclipse.m2e.logback.configuration bundle was activated before the
state location was initialized. Will retry after the state location
is initialized.
Java VM works fine - I can launch (for example) IDEA or java\javac commands.
Any suggestions?
The answer is already here, but it's in the comments. So I re-post it as answer:
check your 2nd screen. Workspace dialogue may be there.
Try this:
1) Remove .snap from:
.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap
If you can't find it manually try this:
find /.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;
It Generally happen when eclipse is closed unexpectedly.
Heres things you can do.!
1)Save and Delete .metadata from workspace folder.
2) Try Re-installing Eclipse.
This solution worked for me. :)
If you don't have any pending changes and have pushed your project already on your repo, you can also try deleting the project folder where eclipse opens a project path automatically.
When you run eclipse again, it will work again.
Unfortunately, deleting metadata didnt work for me. Also I don't have any extra monitor so deleting my project folder was my last resort.

Sometimes keyboard shortcuts do not work in eclipse?

Couple of weeks ago I installed complete ADT bundle from here. this comes up with Android Developer Tool (Eclipse) Build: v22.3.0. Sometimes its shortcut keys do not work. If I close my eclipse and start it again, then it works fine, and if I use to keep work then after some times it again gives the same problem. Is that any bug or issue or did I do something wrong?
Any suggestion?
Its a bug. Happens on windows or sometimes on my ubuntu too. I can not even do a Ctrl + S to save the file. Restarts solves the problem. Its an eclipse bug.

Eclipse does not start when I run the exe?

When I run the Eclipse.exe within the given folder, it will not start. The Eclipse splash screen will appear for a split second then close. There are no errors.
I've tried practically everything. Updating JDK and JRE: I installed JRE 7 and JDK 1.7.0_40. Both 64 bit, and they are both in the (x86) folder. I've tried re-installing them. And re-downloading Eclipse. Same result every time. I've added the VM to the config, still nothing.
I use Windows 7 and the standard Eclipse for Java IDE.
Go to your Workspace folder then go to Metadata > plugins.
Delete everything from this folder. Then it will work.
Warning: This will delete every configuration from Eclipse!
eclipse.exe -clean -clearPersistedState
All you have to do is go the dir where your eclipse.exe is there and run the above command
The same thing was happening for me. All I had to do was uninstalled Java Update 8
go to : "C:\workspace.metadata.plugins\org.eclipse.e4.workbench"
if already you save backup file "workbench.xmi" replace it else delete this.
This also happened to me. I tried some of the solutions above but couldn't get it done. What i have to do was reinstall the JRE/JDK again and it worked!
When i executed the command "java-version" in cmd, i was getting an error trying to load a class and then when i reinstalled JRE/JDK, it worked all good!
I looked online and found a person who had a similar problem.
It says on the forum
"You might need to download JRE 64 bit version"
But again, it depends on what OS you're using as well.
Kindly check the following:
1) Your eclipse version,whether it is compatible with what version of java.
Have that.
2)Check the operating system specific BIT requirements either 32/64 with eclipse version.
3)Usually java will be installed in ProgramFiles for Java if both OS & Java are 64 bit else it will be in ProgramFiles(x86) if java is 32bit and OS is 64Bit.
4)Last but not least check the environment variables for Java whether it meets the requirements of your eclipse version.
Hope this Helps you!
What system you have - 32-bit or 64-bit? You say it was installed into (x86) folder. But normally (x86) is a default for the 32-bit JDK, not for 64-bit JDK. If you used defaults, then it seems that you installed 32-bit JDK instead of 64-bit.
The actual issue should be with the OS architecture, the JDK (32bit or 64 bit) installed and the eclipse type u installed.
Bring them in sync, things would work completely fine.
Just have a check at the Eventlog as mentioned by #Viji
Ideally u should encounter error like RADAR_PRE_LEAK_64
If its a Java version problem, you can edit the eclipse.ini file and assign the compatible version to the application through adding these lines:
windows example:
-vm
C:\jdk1.7.0_21\bin\javaw.exe
for more information:
https://wiki.eclipse.org/Eclipse.ini
Press Win key + X
click 'System' link from popup menu
click advance setting link (Left panel) in opened 'System setting' window (Control Panel\System and Security\System)
Now a window named 'System property' will be open, select 'advance' tab and click on environmental variables
Select path variable from 'System Variable' list section. and click edit
click new button on newly opened window and paste your Jre folder link(Jre in JDK) click okey , okey , okey
re run your program :p
re install your java. First check your OS version.
Just simply uninstall java 8 update 45, it worked for me. Also you might need to delete the metadata of your workspace as I have first deleted the metadata and then uninstalled java 8 update 45.
If eclipse (none of them) doesn't launch at all and there's not even an error message, uninstall Java 8 Updater and reinstall Java 8 from scratch, this should work. Have luck!
Try to install Eclipse into a folder without spaces.
Same problem happened with me . I started eclipse after many days , but it was not starting.just eclipse window flashing , no error nothing. After many trials , i just re-installed my jdk . It worked for me, i think some of my java files were missing or damaged . Try by reinstalling your jdk version it may work as it worked for me.
I tried everything except this. After rigorous trials,Uninstalling java 8 update 25 helped me.
did not have to uninstall Java JDK - just ran installer over my existing install. Not sure what was wrong but this fixed my issue with Eclipse not starting.
I had a similar problem with Eclipse mars. It suddenly over the weekend stopped working and if you ran it from a command window (Windows x64) it would flash up a line or two and then stop.
I installed Eclipse neon yesterday and it worked, but today it stopped working and went wrong in the same way.
Just now I installed the JDK from here:
http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I installed version 8u101 and then neon started. I have not changed eclipse.ini (although I had a look at it) nor have I deleted the plugins (I renamed the folder and found that this had no effect).
Hence I think this difficult to work out problem relates to the JDK/JRE. It would be nice if Eclipse gave a bit more information to go on, but such is life.
I just had this issue in Eclipse Neon. After trying all these suggestions, it turned out that in my case the problem was improperly configured path variables.
There is a pretty good answer already posted here which explains it, but I'll summarize it in this answer for convenience.
You will need to go into your User Environment Variables panel and modify the following values:
JAVA_HOME : C:\Program Files\Java\jdk1.8.0_102
JDK_HOME : %JAVA_HOME%
JRE_HOME : %JAVA_HOME%\jre
CLASSPATH : .;%JAVA_HOME%\lib;%JAVA_HOME%\jre\lib
PATH : your-unique-entries;%JAVA_HOME%\bin (make sure that the longish your-unique-entries does not contain any other references to another Java installation folder.
In my case the problem was not having a proper javabin folder in the PATH variable.
Open the PATH variable and make sure it points to a proper JRE bin folder.
Same thing happened to me.
I was using dual monitor and eclipse opened on my other screen, behind a full-screen window.
I have fixed it by deleting the .metadata/.lock file.
In my case I did see the splash screen hanging at
loading org.eclipse.egit.ui
So I deleted everything starting with org.eclipse.egit within the eclipse\plugin folder
Reinstalling eclipse (newer version) did the trick for me.
Seems to be rare but this happens on windows 10 where the eclipse.exe file is located in a sub-folder which has some UTF-8 folder parent
For example this :
D:\Personal\Idea\دستیار هوشمند بانکی\eclipse doesn't work while
D:\Personal\Idea\Bank AI Assistants\eclipse works.
In my case, moving eclipse to a new fresh machine, I had wrong path of lombok.jar in eclipse.ini
check all eclipse.ini configurations
In System Environment variables , add jdk path in the BEGINNING of the Path
.

How do I prevent Eclipse from hanging on startup?

I am using Eclipse 3.3 ("Europa"). Periodically, Eclipse takes an inordinately long time (perhaps forever) to start up. The only thing I can see in the Eclipse log is:
!ENTRY org.eclipse.core.resources 2 10035 2008-10-16 09:47:34.801
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
Googling reveals someone's suggestion that I remove the folder:
workspace\.metadata\.plugins\org.eclipse.core.resources\.root\.indexes
This does not appear to have helped.
Short of starting with a new workspace (something which I am not keen to do, as it takes me hours to set up all my projects again properly), is there a way to make Eclipse start up properly?
This may not be an exact solution for your issue, but in my case, I tracked the files that Eclipse was polling against with SysInternals Procmon, and found that Eclipse was constantly polling a fairly large snapshot file for one of my projects. Removed that, and everything started up fine (albeit with the workspace in the state it was at the previous launch).
The file removed was:
<workspace>\.metadata\.plugins\org.eclipse.core.resources\.projects\<project>\.markers.snap
try:
cd to <workspace>\.metadata\.plugins\org.eclipse.core.resources
remove the file *.snap (or .markers in Indigo)
In my case (Juno) I had to do this:
find $WORKSPACE_DIR/.metadata/.plugins/org.eclipse.core.resources/.projects \
-name .indexes -exec rm -fr {} \;
That did the trick.
Initially I thought it was a problem with Mylyn (I experienced these freezes after I started using its generic web connector), but the problem appeared even after uninstalling the connector, and even deleting the .mylyn directories.
Edit: I also managed to restart eclipse by deleting just one file:
rm $WORKSPACE_DIR/.metadata/.plugins/org.eclipse.e4.workbench/workbench.xmi
That worked fine, without any indexes involved. Only the workbech, which I personally don't mind that much.
You can try to start Eclipse first with the -clean option.
On Windows you can add the -clean option to your shortcut for eclipse. On Linux you can simply add it when starting Eclipse from the command line.
This one works for me:
Another, and a bit better workaround which apparently works:
Close Eclipse.
Temporary move offending project somewhere out of the workspace.
Start Eclipse, wait for workspace to load (it should).
Close Eclipse again.
Move the project back to workspace.
Source: Eclipse hangs while opening workspace after upgrading to GWT 2.0/Google app engine 1.2.8
I used eclipse -clean -clearPersistedState and that worked for me.
Warning: This may remove all projects from the workspace.
I had a similar problem with a rather large workspace in 3.5 and no .snap-files anywhere to be seen. "Windows -> Preferences -> General -> Startup and Shutdown -> Refresh workspace on startup" seems to be a workspace-related setting and so I couldn't change it for the workspace that was causing the hang.
Running eclipse with the command line parameter -refresh and then changing the setting seems to do the trick.
I also had luck with removing the *.snap files. Mine were located in a different directory than mentioned in the posts (below).
<eclipse workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects
Consequently, the following unix cmd did the trick:
find <eclipse_workspace>/.metadata/.plugins/org.eclipse.core.resources/.projects -name "*.snap" -exec rm -f {} \;
I tried all of the answers in this thread, and none of them worked for me -- not the snap files, not moving the projects, none of them.
What did work, oddly, was moving all projects and the .metadata folder somewhere else, starting Eclipse, closing it, and then moving them all back.
Since I don't have a .snao or .prefs file in .metadata.plugins\org.eclipse.core.resources folder (running on OS X), what did the trick for me was copy the .project folder to old.project, start Eclipse, and check
Windows -> Preferences -> General ->
Startup and Shutdown -> Refresh
workspace on startup
as proposed by matt b. After that, I closed Eclipse, renamed the folder old.projects back to .projects and after that everything worked fine again.
I did this:
cd to .metadata.plugins\org.eclipse.core.resources
remove the file .snap
Noticed the Progress tab was doing something every few seconds..it seemed stuck
Exit eclipse (DO NOT FILE|RESTART HERE OR YOU HAVE TO GO BACK TO STEP 1 AGAIN)
Open eclipse again.
Using -refresh or -clean when starting eclipse did not help.
On Mac OS X, you start Eclipse by double clicking the Eclipse application. If you need to pass arguments to Eclipse, you'll have to edit the eclipse.ini file inside the Eclipse application bundle: select the Eclipse application bundle icon while holding down the Control Key. This will present you with a popup menu. Select "Show Package Contents" in the popup menu. Locate eclipse.ini file in the Contents/MacOS sub-folder and open it with your favorite text editor to edit the command line options.
add: "-clean" and "-refresh" to the beginning of the file, for example:
-clean
-refresh
-startup
../../../plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
Check that the Workspace Launcher hasn't opened on your TV or some other second monitor. It happened to me. The symptoms look the same as the problem described.
Windows -> Preferences -> General -> Startup and Shutdown
Is Refresh workspace on startup checked?
I just had problems with Eclipse starting up. It was fixed by deleting this file:
rm org.eclipse.core.resources.prefs
I found in .settings
UFT causing issues with RDz (Eclipse based) after install
These suggestions will allow to work around this situation even with the environment variables in place and with corresponding values.
Note: Conflicting application will not be recognized in a java context because it is being excluded from the java support mechanism.
Impact: Excludes Add-ins support from hooking to conflicting application executable via Windows Registry Editor
Requirement: The application must be started by an EXE file, except Java.exe/Javaw.exe/jpnlauncher.exe
Instructions:
a. Locate the executable filename of the application conflicting with add-in(s) support. Either use the Task Manager or the Microsoft Process Explorer.
b. Open Windows Registry Editor.
c. Navigate to: HKEY_LOCAL_MACHINE\SOFTWARE\Mercury Interactive\JavaAgent\Modules
For 32bits applications on Windows x64: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mercury Interactive\JavaAgent\Modules
d. Create a DWORD value with the name of the conflicting software executable filenmae and set the value to 0.
Removing *.snap (mine is *.markers), --clean-data or move workspace folder seems all did not work for me.
As my eclipse stopped working after I installed and switched my keyborad input to HIME, I went back to fctix and it worked.
I had no snap files. Going through the help menu installation list, at least 90% of my plugins had the uninstall button deactivated so I could not handle it through there. Under startup/shutdown most of plugins were not listed. Instead, I had to manually remove items from my plugins folder. Wow, the startup time is much faster for me now. So if everything else does not work and you have plugins that are disposable, this could be the ultimate solution to use.
Unfortunately, none of these solutions worked for me. I ended up having to create a new workspace, then imported the existing projects into the new workspace. Unfortunately, you lose your preferences when doing so (so, remember to export your settings anytime you change them!)
I had a very similar problem with eclipse (Juno) on Fedora 18. In the middle of debugging an Android session, eclipse ended the debug session. I attempted to restart eclipse but it kept haning at the splash screen. I tried the various suggestions above with no success. Finally, I checked the adb service (android debug bridge):
# adb devices
List of devices attached
XXXXXX offline
I know the android device was still connected but it reported it offline. I disconnected the device and shut down the adb service:
# adb kill-server
Then I waited a few seconds and re-started the adb service:
# adb start-server
And plugged my android back in. After that, eclipse started up just fine.
no need to delete entire metadata file. just try deleting the .snap file from org.eclipse.core.resources on your workspace folder
ex. E:\workspaceFolder\.metadata\.plugins\org.eclipse.core.resources
Watch out for zero-byte .plugin files in the {WORKSPACE-DIR}/.metadata/.plugins folder. I just deleted one in there and it fixed my freezing issues.
In my case similar symptoms were caused by some rogue git repository with a ton of junk system files.
Universal remedy, as mentioned above, is to use Process Monitor to discover offending files. It's useful to set the following 2-line filter:
Process Name is eclipse.exe
Process Name is javaw.exe
I had a similar problem after I updated eclipse on Mavericks. Eventually I found that in the eclipse plugins directory the com.google.gdt.eclipse.login jar had version numbers at the end. I removed the version number from the name and it all started fine :)
Also look at http://www.lazylab.org/197/eclipse/eclipse-hanging-on-startup-repair-corrupt-workspace/
99% Recommended Solution works.... (i.e. Removing .snap file) But if it did not worked then we have to try to remove indexes folder and further workbench folder.
This may help
In your eclipse,
1) Go to Help
2) Click Eclipse marketplace
3) search - optimizer
install "optimizer for eclipse"
In Ubuntu eclipse -clean -refresh worked for me for Eclipse 3.8.1
It can also be caused by this bug, if you're having Eclipse 4.5/4.6, an Eclipse Xtext plugin version older than v2.9.0, and a particular workspace configuration.
The workaround would be to create a new workspace and import the existing projects.
Well, I had similar behaviour while starting eclipse over X11. I forgot to tick the enable X11 forwarding in my putty.
In my case deleting the .metadata folder of the workspace worked. I am using Eclipse Luna service Release 2.

Categories