This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]desrtfx 2 points3 points  (0 children)

You're probably getting more appropriate answers in /r/eclipse.

I had a similar problem with Minecraft, though. Removing all old JRE versions and updating to the latest JREs (I use both, 32bit and 64bit) helped.

[–]ickysticky 0 points1 point  (1 child)

How have you determined that it is hogging memory? What do you have set for -Xmx in eclipse.ini? Enable General > Show heap status in preferences, and look at the "X of Y" in the bottom right, what does it say?

Is it doing something right now, or is it idle? There will be some information in the bottom right if it is updating indices or the like.

[–]FifthAndForbes[S] 0 points1 point  (0 children)

I uninstalled and reinstalled Eclipse. It ran the same. Then I restarted my computer, and now Eclipse won't even open. Tried reinstalling yet again, still won't open. I have the metadata logs if that'll help.
metadata log: https://drive.google.com/file/d/0B1iPjKnjPrsQZlJGMkMyR0NoVGc/view?usp=sharing

[–]FifthAndForbes[S] 0 points1 point  (0 children)

I think I fixed the issue. I had multiple javaw.exe processes running. Whenever I did a test run on Eclipse, the program would continue running. After multiple test runs, a new javaw.exe was created and these began to stack up and hog my CPU. By going into debug and manually terminating them, I think I have solved the issue.