gcj/SWT gc() and memory

Sat Jun 19 23:59:00 GMT 2004

You are observing the large heap size under Windows? Or also
under Linux?
If it's under Windows, you might be running into a known issue
with the collector scanning graphics memory for roots. You
can get more information about what's going on by either calling
GC_dump() explicitly, or by running the executable with
the GC_DUMP_REGULARLY environment variable defined. Especially the
latter will produce huge volumes of output. You are really interested
in its description of the root set after the heap has grown.
Hans
> -----Original Message-----
> From: java-owner@gcc.gnu.org 
> [mailto:java-owner@gcc.gnu.org]On Behalf Of
> Heitzso
> Sent: Saturday, June 19, 2004 10:02 AM
> To: java@gcc.gnu.org
> Subject: gcj/SWT gc() and memory
>>> I have a SWT 3.0RC app that generates hundreds of
> thousands of small short life objects, plus some larger
> objects. Run under Linux (IBM JRE) or Win (Sun JRE)
> it stabilizes out around 32M. The same code compiled
> to native with gcj stabilizes around 100+M. I need
> to be able to run on old Win98 128M machines so 100+M
> is too large.
>> Is there a better garbage collector I should be
> turning on or using?
>> I'm starting this app up off CD and on a slower
> CDROM cranking up the JRE off CD is _slow_, hence
> I have a strong desire to use the gcj compiled
> version.
>> Thanks for any advice,
> Heitzso
>>> -- 
> Heitzso
> 770-538-0963; Mobile: 770-654-5098
>