[jcorbin4607]

I am having a heck of a time trying to debug my application because the MyEclipseIDE environment keeps locking up.

The console statements from the server (JBOSS 4.0.2) are displaying at a snails pace…very,very slow. Not sure if that is an application specific threading issue or not. Doesn’t seem to be happening to anyone else on my team with the same source tree.
It also takes quite a while to get to the next line of code in the debugger when stepping over.

Sometimes I get debugger errors mentioning stack frame issues. I wonder if my startup memory requirements for both MyEclipseIDE or JBOSS Server may be an issue.

MyEclipseIDE startup: -Xmx512M

JBOSS Server JDK startup: -Xms512M, -Xmx512M

Here is some version information:

OS
Windows XP SP2
1GB RAM

Eclipse
Version: 3.1.1
Build id: M20050929-0840

MyEclipseIDE
Version: 4.0.3
Build id: 20051025-4.0.3-GA

MyEclipseIDE Compile Time JDK: Sun Java 1.5_02
Server (JBOSS) JDK: Sun Java 1.5_02

[Riyad Kalla]

I would encourage you to set -Xmx256 for MyEclipse, and the same for JBoss. My guess is that your VMs are actually growing to 512, but keep in mind Windows and your other software running (virus scanners, whatever) are going to take about 100mb right off the top, if you use firefox and any number of tabs, there goes another 100mb. So by you telling jBoss and MyEclipse that they can grow to 512 each, if they DO grow that large, Windows is going to start paging out massive amounts of ram to disk, and all the sudden your debugging sessions has become a nightmare’s worth of windows swapping information to disk so MYEclipse and JBoss can grow. Keep in mind because of the overlap of all of this, simply using ME and JBoss can cause them to swap parts of themselves out and back again over and over again.

Now if you adjust all that and debugging is still slow, make sure any projects you don’t need are closed. Debugging scans all open projects for possible break point hits.

[Author]

Posts