A
Alan Morgan
I have a Java app, running on Windows, with a medium amount
of C++ wrapper code doing various arcane and boring things.
JProfiler swears that there isn't a memory leak in the Java.
Purify claims that there isn't a memory leak in the C++. According
to ProcessExplorer, however, we leak memory (or rather, the
Private Byte and Working Set keep rising). Some of this might
be induced by memory fragmentation, I suppose, but other than
that and the thought that Sun's JVM might leak memory (possible?),
I'm not sure where to go.
I'm currently using Sun's 1.5 JVM. Client and Server mode doesn't
make much of a difference (the amount of memory used goes down,
but the increase remains). I haven't tested extensively with 1.6,
but saw essentially the same behavior with my quick look.
Is futzing with the GC parameters going to accomplish anything?
Is this just expected behavior? Is the only solution to kill and
resume the app on a regular basis?
Alan
of C++ wrapper code doing various arcane and boring things.
JProfiler swears that there isn't a memory leak in the Java.
Purify claims that there isn't a memory leak in the C++. According
to ProcessExplorer, however, we leak memory (or rather, the
Private Byte and Working Set keep rising). Some of this might
be induced by memory fragmentation, I suppose, but other than
that and the thought that Sun's JVM might leak memory (possible?),
I'm not sure where to go.
I'm currently using Sun's 1.5 JVM. Client and Server mode doesn't
make much of a difference (the amount of memory used goes down,
but the increase remains). I haven't tested extensively with 1.6,
but saw essentially the same behavior with my quick look.
Is futzing with the GC parameters going to accomplish anything?
Is this just expected behavior? Is the only solution to kill and
resume the app on a regular basis?
Alan