Red Hat Bugzilla – Bug 128309
Degrading java performance after repeated debug sessions
Last modified: 2006-10-13 14:34:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7)
Description of problem:
Installed JRE: java-1.4.2-ibm-220.127.116.11-1jpp_8rh
Target OS: Red Hat Enterprise Linux WS - U2
Developer Suite: 2.0
Over repeated debug sessions on run->debug as runtime workbench, the
target (inferior) workbench takes longer and longer to launch, and
becomes increasinly sluggish. javaw often takes up 100% processor time
on launch for upto 3 minutes (normal launch times should 10-20
seconds). Killing eclipse (and it's supporting jvm process) does not help.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Retrieve plugin (any) project
2. Run->Debug as Runtime Workbench
3. Repeat several times
Actual Results: The launched debug workbench becomes increasingly
less responsive, takes up considerable processor time to launch,
Expected Results: The launch and responsive times of the debug
workbench should remain constant across all sessions.
Usage of the bea jvm does not improve performance (it might a little
bit). Usage of Sun's JVM seems to improve performance quite a bit.
There is no indication of which eclipse package is being used here and RHDS 2.0
is old and unsupported. Closing bug.