This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Fwd: readObject memory consumption
- From: Nicolás Ernesto Kuzminski <nkuzminski at gmail dot com>
- Cc: java at gcc dot gnu dot org
- Date: Tue, 30 Nov 2004 23:47:12 -0300
- Subject: Fwd: readObject memory consumption
- References: <dfe7d5d204113011494dcdd64f@mail.gmail.com> <m37jo3oud2.fsf@localhost.localdomain> <dfe7d5d204113018414db9f19a@mail.gmail.com>
- Reply-to: Nicolás Ernesto Kuzminski <nkuzminski at gmail dot com>
On 30 Nov 2004 15:16:41 -0700, Tom Tromey <tromey@redhat.com> wrote:
> I don't think I was aware of this as a problem. Filing a PR, with the
> test case (and preferably some data on our memory use and how it
> compares to, say, the JDK) would be helpful.
Ok, I can give it a try..
And yes, I did the same on JDK 1.4.2 and it worked flawesly. I mean,
the process took almost the same few megas for serializaton and
deserialization, considering that on this testcase no objects are
maintaned alive. With GCJ, yo can see that the serialization works on
this example on the same grade, but the deserialization takes big
amounts of memory very fast. And, if the jvm keeps working, that
amount is not ever returned back. That's what's happening on my app.
Sort of leakage on the runtime.
I have no expierence debugging this things. Who know, maybe its time
to learn new things...
--
Saludos, Nico.