Community
Participate
Working Groups
3.2M2 - launch Eclipse - on MacOS X start "Quartz Debug" and turn on Flash Screen updates Observe: the full HeapMonitor control in the status line is redrawn at least once a second and even if the value hasn't changed. At least redrawing the trash can could be avoided...
Redrawing it once per second affects performance on my PowerBook in the range of a few percent. I think we should only enable the HeapMonitor if its performance impact is neglectable (on all platforms).
I have some code to make the monitor not refresh during idle. It will only refresh if the previously displayed value is different to the value to be displayed by more than 1 meg. This value could be increased if needed. Changing the update interval to 1-2 seconds would have a way bigger impact though. For various reasons, i am unable to create a patch. Is it ok it i attach the modified java file (from 3.2 M2)?
Brock, attaching the full file would be fine, and thanks for your help.
Created attachment 27918 [details] Modified HeapStatus.java Also contains a fix for bug 111409 which you may want to remove.
tc - could you review/apply the patch?
The patch removed the fix for Bug 110728 which I restored but it was otherwise fine. Released in build >20051011
*** Bug 111393 has been marked as a duplicate of this bug. ***
Verified in 20051101
Sorry to be the bearer of bad tidings, but on the same hardware for which I reported bug 110728, I now find: Eclipse 3.2M4 on Mac OS X 10.4.3 is using 0.10% of the CPU when at idle with the heap status trim off, but uses 15-30% at idle with it on. Should I open another bug? I can provide Activity Monitor samples if you wish.
Please reopen this bug.