libgcj/353: Memory Leak

[Bryce McKinlay]

The following reply was made to PR libgcj/353; it has been noted by GNATS.

From: Bryce McKinlay <bryce@albatross.co.nz>
To: Heinz@chanet.de
Cc: java-gnats@sourceware.cygnus.com
Subject: Re: libgcj/353: Memory Leak
Date: Tue, 10 Oct 2000 13:15:03 +1300

 Heinz@chanet.de wrote:
 
 > I'm trying to evaluate using java via gcj to write Linux background damons. So far so good, my biggest problem are memory leaks. Calling the Process.exec method results in heavily increasing program size. That's for native compiled programs (.java or .class as source does not matter). java interpreted bytecode is ok.
 
 I can't reproduce this. Using a recent cvs tree, memory usage for your test program remains constant at 4200K (2908K shared) on a RedHat 6.2 system.
 
 It is possible that this is a bug in the libgcj 2.95 version you are using. I reccommend updating to a recent cvs/snapshot version of gcj & libgcj, or the one that ships with Red Hat 7.0.
 
 regards
 
   [ bryce ]