Community
Participate
Working Groups
using i0420 and IBM 1.4.2sr1a -Xj9 I have one dev and one target Eclipse. While the target is running a plugin export (essentially a mess of Ant scripts), the dev debugger is churning away taking about 6-8% of the CPU and burning about 1MB for heap per second. Once in a while I catch a glimpse of a progress message (bottom right) saying Debug Event Dispatch (or some such). If the target hits a break point or finishes, the memory and CPU churn stop. Note that I have something like 2-5 breakpoints. all are "conventional". No conditional, method entry/exit, no watches, ... I have rebooted the machine, restarted all Eclipses etc. Nothing seems to change this behaviour
I don't see the same amount of burn or CPU usage. I get a memory increase of about a 1MB and CPU usage around 2-3%. My heap and cpu usage are caused by thread start and thread death events. 6-8% and 1MB/s sounds high for just these thread events though.
No specific action planned for 3.1. Still open for investigation.
I don't see this churn in 3.3 during the entire export of two plug-ins from a target workspace the host workspace alloacted only 1M.
Marking as works for me.
