I recently installed/updated eclipse environment. When I try to compile the code I'm getting the error as:
Unhandled event loop exception
and says the error is in the org.eclipse.ui plugin-in.
Can any one help me on this?
Ok please follow the following steps:
First close your eclipse.
Go to your Eclipse Folder
You will find the "Features" & "Plugins" folders in it.
Open the "Features" folder and search for the "org.eclipse.ui" folder or .jar file. If found then cut it & paste on desktop.
Open the "Plugins" Folder and search for the "org.eclipse.ui" folder or .jar file. If found then cut it & paste on desktop.
Now start your eclipse & try to compile.
It's possible that while updating it has downloaded the wrong updates.
Finally after spending 2 hours trying to fix Eclipse, I just re-installed Eclipse and everything worked in the following 15 minutes.
no need to worry.. if you running android application.. give eclipse some time... restart your computer after some times open eclipse clean all projects.. now try.. it working perfectly now.. :D
Cleaning all projects worked for me!
I also had "Unhanded event loop exception" in Eclipse neon.3 on Linux Mint, and there were other problems such as the perspective button bar either not showing or else throwing an error when you attempted to configure it.
I found the solution in comment #7 of an Eclipse bug discussion.
The solution is to start eclipse after first executing these commands:
export SWT_WEBKIT2=1
export SWT_GTK3=0
The solution here was not working for me but after digging through the internet it became clear that some other software is messing up eclipse.
In my case it was the hydra vision in the catalyst control center. As I can see any application that messing with window handling will or can cause this error, based on the variety of setups and background from other people who experienced this problem.
One of the best ways to determine which application is causing the problem (if it's an applicaion) is:
open the task manager
start killing processes (start with unknown or new or any video related driver).
After each process kill check eclipse (restart it each time, just in case)
and after killing hydra vision the error did not pop again (no restart was needed but who knows how other application works).
Hope this will help others to not spend a day on this annoying problem.
Best for all
In conjunction to cleaning all of the projects as suggested by Michael Martin, I also appended this line in the eclipse.ini:
-XX:+UseConcMarkSweepGC
Per this documentation.
Related
Every time I run Android Studio, this loading screen pops up, but Android Studio stays here and doesn't load. It's like this following picture except that the loading bar is loaded all the way but stuck there. I am running Windows 10.
I have tried many things, including setting the system variables JDK_HOME to where my JDK is located and the same for JAVA_HOME. I have also set a path. I ran as admin many times and let AS through a firewall.
I have also restarted and reinstalled countless times.
The version of AS is 2.0, and I am running the latest versions of Java.
Any help?
Open file Android Studio setup directory/bin/idea.properties
Add disable.android.first.run=true to end
Restart Android Studio
PLEASE NOTE: This will break patch updating to the next version. We
now check full binary checksums on the whole installation to prevent
various install corruption bugs as well as to preserve application
signatures. Therefore, make a copy of this file first, and before
updating, put it back.
Please try the following method to fix that issue:
Find the folder of your AndroidStudio: based on the following directory
macOS: ~/Library/Application Support/Google/AndroidStudio[version]
Delete the AndroidStudio folder.
Restart
Ref:https://developer.android.com/studio/known-issues#studio-config-directories
In order to know how to debug the problem, I executed the bin\studio.bat script in the terminal and inspected the actual Idea exceptions in order to fix the problem.
For me, this was the issue:
ERROR - llij.ide.plugins.PluginManager - java.net.BindException: Address already in use: bind
java.util.concurrent.CompletionException: java.net.BindException: Address already in use: bind
This means the plugin manager is trying to listen on a port that is not available. Is something listening on that port? For me, it was the stupid "excluded ports" by Windows, so I simply stopped the service:
net stop winnat (as administrator), and confirmed that Android Studio started to work.
No need to re-install, delete precious configuration (and plugins, etc.). Just read the log provided by the bin\studio.bat script, and I was able to fix the issue.
I'm on Windows. I created a new project on Android Studio for Marshmallow at least.
The only thing I've done so far is generating the main activity which is a tabbed activity with view pager. Also, you should know that this project is a private git repo that I cloned.
I'm working on this project with another developer and the project is perfectly working on his side.
The problem is:
When I try to launch the app (wether it is a virtual device or my real phone), the gradle build gets stuck at the app:processDebugResources step. I waited more than an hour and nothing happened. Moreover, when I want to cancel the gradle build, it doesn't respond and I have to kill Android Studio process. Then I restart Android Studio and I have to kill a gradle process that prevents the initial gradle build (at Android Studio startup) from working.
The crazy thing is that I was able to launch the app before. I even installed it on my phone!
What I've tried so far:
Do what stackoverflow was giving as solutions like tick the offline mode in the settings
Create a new project --> It doesn't change anything
Reinstall Android Studio --> It doesn't change anything
Deactivating Avast antivirus
Invalidate cache/restart + Clean + rebuild (the rebuild gets stuck like when I try to launch the app)
And maybe other solutions that I forgot...
It's getting very annoying as it's making me lose days of development.
If you have any more solutions, or if you think I should try again some of the previous solutions, help would be greatly appreciated !
I know this is an old post, but I faced the same problem during the last few days and since i got crazy I hope I can help someone else out there.
After many hours of troubleshooting I found that the Java Platform SE binary executable goes in "suspended mode" in Windows 10, preventing Android Studio from compiling (it hangs at app:processDebugResources).
Example Screenshot
Killing the suspended process and recompiling the project works just fine... until Java gets suspended again.
Maybe your gradle version is not compatible with it. Try again with latest version of gradle in your project.
I did several things:
Install NDK
Change JDK from embedded one to Jdk 8
Redownload SDK i was using (6,7,8)
And now the problem is solved ! I have no idea which of these things made the tricks but I'm happy ! It may be useful to someone else one day.
I don´t know what I did... Everything was working well, had to battle a while to get facebook login working, and doing what I wanted to do... Finally it was ready, so I proceeded to Export Android Application... First error had to do with Dalvik code error 1 something... So I look for duplicates .jars in my folder, erased libraries in java build path, cleaned the project, etc, as proposed in some stackoverflow answers...
Stopped getting that kind of error but now I can´t even Run the application, now I get some errors like: Unable to execute dex: GC overhead limit exceeded, or: Unable to execute dex: Java Heap Space.
In my windows machine it gets stuck until some memory related error is displayed... in my Mac the Eclipse is forceclosed in most occasions ... I tried to roll back and took off the facebook sdk part, but nothing, now I can´t run/export my app even as it was before... I guess I did something wrong in the cleaning or something in the Eclipse parameters..
Please help, I´m dying here.. Thanks.
Answering myself to help others:
1.Check there´s no duplicate .jar anywhere in your project.
2.Go to eclipse.ini in your Eclipse folder, and modify to this, or greater:
-Xms512m
-Xmx1024m
3.Save and restart Eclipse
4.Go to Project -> uncheck Build Automatically
5.Go to Project -> Clean... , clean both the library project and your app project
6.Export your app as a signed APK while Build Automatically is still disabled
7.Re-enable Build Automatically and everything should be back to normal as before
These are the errors that i am getting when i attempt to run my project. It was working perfectly fine till yesterday. I have no idea what is causing the error. I cleaned the project and reran a number of times. I even restarted my laptop, but in vain. Please help me restore this, its a very huge project.
My friends copied the project on his laptop and was able to run it successfully. Which concludes that there has been a problem with my eclipse.
There are too many errors to sort out. I would very much recommend the easy way out which is to uninstall Eclipse (in case it really is the source of the problem) re-install it and start up a new project, then slowly add in the project files one by one. At least this way if the error comes back you know which file it is (if any). Best of luck.
Try to update eclipse if there is any update to apply.
Ever since updating my android sdk and eclipse plugin, I cannot see the values of local variables while debugging in eclipse. This worked fine previously. Has anyone else experienced this and found a solution?
Late edit, but an important note:
This only happens for classes in projects marked as "Is Library". I have 2 projects, one of which is marked as an android library, the other of which utilizes this library. When I run an activity from the second project, I can evaluate local variables for its classes but not the library classes.
Sometimes, I have the problem that I have to reboot Eclipse cause it is not connecting correctly to the emulator(or the device) on debug-mode. Otherwise, you can also try by going to your
/android-sdk/platform-tools/
folder and there, run adb.
You can try to reboot the demon and so on by running
adb kill-server
and after, start it again by:
adb start-server
Hope it is going to work.....Otherwise the other solution could be to reinstall the Android plugin to see if there was a problem there....
Try one of the two things:
Window -> Reset perspective..
Just close that "Variable" window and reopen.
Would you like to share the code with us?
Try with
Window>Preferences>Java>Compiler>Compliance and Classfiles
check ON "Add variable attributes to generated class files (used by debugger)"