Detecting memory leaks

Hans Boehm Hans.Boehm@hp.com
Thu Sep 23 03:49:00 GMT 2004


A good first step is probably to determine whether the GC heap or the C
heap is growing.  Setting the GC_PRINT_STATS and/or GC_DUMP_REGULARLY
environment variables should tell you that.  (The latter produces lots of
output on large GC heaps.)

Hans

On Wed, 22 Sep 2004, Jari Korva wrote:

> Hi,
>
> are there any easy to use tools for finding gcj memory leaks, especially
> on ARM/XScale? For example the following code seems to leak on
> armv5l (gcj 3.4.0) and armv5b (gcj 3.4.2), but not on x86 (gcj 3.4.0):
>
> import java.net.*;
>
> public class MemLeakTest
> {
>     public static void main(String args[])
>     {
>         for(;;)
>         {
>             try {
>
>             URL url = new URL("http://princess.willab.fi:8111/");
>             URLConnection conn = url.openConnection();
>             System.out.println(conn.getContentType());
>             conn.getInputStream().close();
>
>             } catch(Exception e) {
>                 e.printStackTrace();
>             }
>         }
>
>     }
> }
>
> Cheers,
>   Jari
>
> --
>  - Jari Korva -
>



More information about the Java mailing list