Since a week or two, Eclipse becomes very slow after resuming Windows:
Scrolling becomes very slow: the scrollbar and line numbers scroll at a different speed than the text. Then I need to wait for the text to catch up.
Typing is very slow. I'd guess there's a 500ms delay
Running code is very slow. The unit tests for my current project typically take around 5 seconds. After resuming Windows, this is systematically over 20 seconds.
Opening or saving a sourcecode file takes longer (several seconds)
However, navigating menus doesn't seem to be slower than before.
Restarting Eclipse doesn't help, though I notice it starts up quicker than after a clean boot, which makes me believe it doesn't shut down completely.
Other Java apps don't appear to be slower.
In case the problem can't be found, is there some way I can force Eclipse to restart cleanly?
Related
My Qgis is behaving terribly slow the last few months. Opening takes minutes, trying to switch between the layers panel and the browser panel takes minutes, selecting an arcgis featurelayer takes minutes, trying to add data takes minutes, closing takes minutes. Pretty much everything takes a long, long time.
I tried removing Qgis and all asociated files and re-installing it, but no luck. I tried a fresh profile: no luck.
What else can I do?
I also had this issue, especially with switching between Layers and Browser panel. I solved this with acitivating Fast Scan this directory option from the context menu in the Browser panel for all the hard drives I'm using.
All of a sudden my breakpoints won't work for my Eclipse Mars project.
I set them - and it even asks if you want to go to debug perspective when the app gets to a breakpoint - but you can't actually see it stop at the breakpoint. It's like it's stopping - but you can't see the highlighted lines.
I've tried cleaning everything out and re-building multiple times. Still the same.
Any suggestions?
Thanks
Apparently that can happen when your disk space is extremely low.
I'm switched to idea from eclipse recently,the biggest question which make me uncomfortable is the auto popup completion is a little slower then eclipse.
In setting page,i set all possible delay to 0 but it's still slower than eclipse.
And i have noticed that if something(field,method,class...) be reference after first time,it's prompted to be faster,but after a few secends,it's will become slow again,maybe 100~300ms
The eclipse auto-completion is nearly have no delay when i set delay to 0,so how do i raise the speed of idea code auto-completion?
Just got a new MBP, not upgraded from a previous version, and trying to get through a few issues with the new OS and programs.
One oddity that I'm having is with eclipse, in some of the menus, the Variables/Expressions window and the console, some times. I've included screenshots of it occurring in the debug windows and menu, wasn't able to catch it in the console as that's the inconsistent one. What occurs there is it looks fairly normal, all ok, but when I bring focus to it, it goes all weird,
Got it after playing around with the colours and fonts, as described How can I change font size in Eclipse for Java text editors?
Something's definitely messed around because while most things were set right, at 11 or so, they were displaying at 5. When I then explicitly set them to 11 and restarted, they came back huge. Then resetting them put everything back to normal. shrug
I'm debugging someones code, and it freezes when I do something specific, but Eclipse doesn't stop on an error (I may have accidentally turned this off). When I press pause in the debugger, Eclipse shows me a bunch of suspended threads, where two of them are coloured red.
I want to find out if there is an error anywere, or if there's just an infinite loop somewhere (which doesn't seem likely, because Eclipse should break in the loop in that case).
I'd be great if anyone can help me with this Thanks in advance!
Maybe you have a deadlock?
You can use jconsole (goes with java jdk) to find out this. Launch jconsole, attach to your process, go to the Threads tab. Press "Detect deadlock"... It can be also useful to look at all threads states, for example you can have infinity loop in one thread and another thread blocked etc...
I've had this happen to me before, try inserting breakpoints every few lines of code, then stepping through those until it breaks, removing the breakpoints that don't have any errors between them. Remember the line of code that causes it to crash and make whatever changes are necessary to fix it.