[kaffe] memory leak in jit3 ?
stack at cs.utah.edu
Sun Dec 29 14:52:14 PST 2002
On Sunday, December 29, 2002, at 08:03 AM, Dalibor Topic wrote:
> Hi Tim,
> You need to apply the GNU Classpath java.util.zip
> replacement patch, available at
> and to copy the Klasses.jar.bootstrap file over the
> existing copy in libraries/javalib. After installing
> the patched version of kaffe, simply running its jar
> tool on rt.jar as in
> kaffe -verbosemem kaffe.tools.jar.Jar xvf rt.jar
> should show more than 3 MB of jit-temp-data.
Yep... the problem? The jitter sucks :).
The thing thats tickling the bug is the static initializers
in UnicodeTbl/UnicodeIdx. They are so large that they
need a ton of memory to be compiled. So they force
the jitter's label/const/seq object pools to be grown to
an enormous size. Since these are not bounded, they
end up staying around for the rest of the run.
As for possible solutions? The quick and dirty way
would be to just bound the pool sizes to some
reasonable limit. The best solution would be to fix
the jitter since the peak usage is still ginormous.
> best regards,
> dalibor topic
More information about the kaffe