[harryajh]

using ME 3.8.4+QF2 in Eclipse 3.01, win 2000(sp4)

When I use the debugger every line I step over a line it takes 5-6 sec’s to move to the next, the CPU usage goes up to 100% each time.

This is totally unbearable & I’ve had to resort to using “System.out.println” statements – have you any idea what might cause this?

thanks

[Scott Anderson]

Harry,

It’s likely caused by not having enough RAM alloated for Eclipse to use. You can fix that by changing the commandline arguements to something like:
eclipse.exe -vmargs -Xms128M -Xmx512M

[harryajh]

thanks for that, got it set to “-Xms256M -Xmx512M” & seems to have made a difference.

Still takes 2/3 sec’s (better than 6 though!) per statement & cpu usage still hits 99% – is there anything else I could try or is this normal?

thanks

harry

[Scott Anderson]

Still takes 2/3 sec’s (better than 6 though!) per statement & cpu usage still hits 99% – is there anything else I could try or is this normal?

It could be normal. The rate the Eclipse debugger steps seems to be impacted by number of breakpoints that are turned on as well as whether or not any of them is conditional or has a “# of times” trigger (these last two seem really slow).

[harryajh]

back to square one again for some reason?, using these command line args -vmargs -Xms256M -Xmx512M & 6-8 sec’s per statement to step over, cpu goes up to 99%!

Have noticed doing a netstat -s shows hundreds & hundreds of “active connections” 887 currently but have seen well in to the thousands- could this be anything to do with? – ran several spyware scanners & virus checkers & am sure machine is totally clean!

totally fed up, totally depressed, J2EE must be the only technology that gets harder & harder the more you do it!

any ideas?

thanks in advance

harry

[Author]

Posts