|
From: <no...@so...> - 2002-02-25 05:43:14
|
Bugs item #522331, was opened at 2002-02-24 21:43 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=438935&aid=522331&group_id=44253 Category: Performance Group: Serious Status: Open Resolution: None Priority: 5 Submitted By: Brian Stoler (brianstoler) Assigned to: Brian Stoler (brianstoler) Summary: Massive memory leakage Initial Comment: I think DrJava is leaking memory. I just started getting some OutOfMemoryErrors when compiling something in a long-running DrJava process. That process was using 105 MB of memory. I then started a new DrJava process, and it's using 32MB of RAM. (Note that all of this only is concerning the main JVM; the interactions JVM is a whole other game.) I think it's leaking memory. Let's see how process RAM use changes as I compile, to see if that's what is leaking memory: OK, loaded one file, and memory use went up less than a megabyte. Now I compiled it once, and memory use went up to 48MB. Compiled the same file again, and memory use is now 52MB. Further compiles of the same file: 55, 58, 61, 64, 66, 70, 73, 76, 80, 84, 87, 89, 92, 96, 99, 100, 103, 106, 108, and the next one causes an OutOfMemoryError. I think this is a memory leak cause by compiling. :) ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=438935&aid=522331&group_id=44253 |