| debugging has become a pain in eclipse [message #139961] |
Fri, 24 February 2006 06:30  |
Eclipse User |
|
|
|
hello all,
recently eclipse has started to behave a little strangely. when i launch
my application from within eclipse in debug mode, my application goes
extremely slow, eating all the processing power(100% activity in task
mgr!). but when i launch it normally from within eclipse, my app runs
smoothly.
can any1 plzzz help me out on this. my bo$$ is asking me to leave this
tool alone and start using jbuilder 2005 as he has a spare license. but i
prefer eclipse, and if this issue isnt resolved i'd have to cave in.
|
|
|
|
|
|
| Re: debugging has become a pain in eclipse [message #140089 is a reply to message #140046] |
Fri, 24 February 2006 11:20  |
| Eclipse User |
|
|
|
kevin,
im using eclipse 3.1.2 with jdk1.5.0_06 on windows platform. i've also got
a snapshot of mustang with me and i tried launching my app with tht
jre(mustang snapshot 9 i think). but the prob remained the same. my
machine is a 2 ghz intel centrino/512 ram running winxp pro.
i cant give sample code for several reasons. firstly, its not a piece of
code i can point to that could be causing the problem. secondly, my boss
wouldn't like me giving away some/part of the code^_^.
here's the scenario. i launch eclipse. open my project(usually already
opened). then i debug my application, which launches the application just
fine. when i'm working with my application, such as selecting a menu,
clicking a menu item, etc. the application eats up all of my processor.
task mgr shows 100% cpu being used by javaw.exe. and sadly, when i shut
down eclipse(by killing its process) my application suddenly starts
behaving normal,i.e becomes responsive.
interestingly this didn't use to happen a few days ago. i wonder what is
causing this. i'm not using any firewall on my machine.
any thoughts?? have done a lot of googling around but no answers so far.
can you or any of the gurus out here help?
thanks.
|
|
|
| Re: debugging has become a pain in eclipse [message #140828 is a reply to message #140089] |
Tue, 28 February 2006 12:20 |
| Eclipse User |
|
|
|
Originally posted by: daniel.megert.eclipse.org
Haris wrote:
> kevin,
> im using eclipse 3.1.2 with jdk1.5.0_06 on windows platform. i've also
> got a snapshot of mustang with me and i tried launching my app with
> tht jre(mustang snapshot 9 i think). but the prob remained the same.
> my machine is a 2 ghz intel centrino/512 ram running winxp pro.
>
> i cant give sample code for several reasons. firstly, its not a piece
> of code i can point to that could be causing the problem. secondly, my
> boss wouldn't like me giving away some/part of the code^_^.
>
> here's the scenario. i launch eclipse. open my project(usually already
> opened). then i debug my application, which launches the application
> just fine. when i'm working with my application, such as selecting a
> menu, clicking a menu item, etc. the application eats up all of my
> processor. task mgr shows 100% cpu being used by javaw.exe. and sadly,
> when i shut down eclipse(by killing its process) my application
> suddenly starts behaving normal,i.e becomes responsive.
> interestingly this didn't use to happen a few days ago. i wonder what
> is causing this. i'm not using any firewall on my machine.
Maybe virus scanner? I suggest to create a bug report and attach stack
dumps that you create during the 100% CPU phase.
Dani
>
> any thoughts?? have done a lot of googling around but no answers so
> far. can you or any of the gurus out here help?
>
>
> thanks.
>
|
|
|
|
|
| Re: debugging has become a pain in eclipse [message #143078 is a reply to message #141094] |
Tue, 14 March 2006 16:16 |
| Eclipse User |
|
|
|
Originally posted by: eclipse.vanderberg.fastmail.fm
I too have been suffering this issue intermittently during debugging. I
tried the suggestion below, and it did not seem to help. I did however
find that removing all my breakpoints and starting over with just the few
breakpoints I needed dramatically improved debugging speed.
Matthew Laurenson wrote:
> Haris
> I was observing similar behaviour to yours with remote debugging, but seem
> to have sorted it just now. The problem for me was the "Source Lookup
> Path" in Eclipse on the Source tab under Run Debug...
> By default the source path contained a large list of jar files, most of
> which didn't have any source anyway. I removed the "Default" entry, and
> added in just my project source folder. This made an incredible difference
> to the speed of execution (something that took 30 minutes now takes 10
> seconds).
> I had tried turning off hyperthreading...
> Good luck with sorting out your problem.
> Regards
> Mattthew
|
|
|
Powered by
FUDForum. Page generated in 0.08975 seconds
Home