> From: Chris Abbey <[EMAIL PROTECTED]>
> ...
> But is that [X server] memory allocated out of the chunk of VM reserved as the HEAP?
> I doubt it... I don't think it even blongs to the same process does it?
Right. It might be on a completely different machine.
Daniel
Nelson Minar writes:
> javares. Info is at http://gee.cs.oswego.edu/dl/javares/
The archive seemed to cover the first two weeks only?
> There's room for a good project here. There are some partial solutions
> now, JRes is probably the best known one.
The web site referred to in one of the ar
> > javares. Info is at http://gee.cs.oswego.edu/dl/javares/
>The archive seemed to cover the first two weeks only?
No, that's the full archive. My impression is a lot of people are
interested in the problem but not many people are working on it.
>>There's room for a good project here. There are
If you're interested in Java resource management, I encourage you to
carry on the discussion on a mailing list I run for just that purpose,
javares. Info is at http://gee.cs.oswego.edu/dl/javares/
There are lots of people who are interested in this problem - real
time folks, people running untrus
"Daniel W. Dulitz x108" wrote:
> Rob Clark writes:
> > Here's a crazy idea: the whole problem, as I see it, arises because
> > the JVM's garbage collector only knows of one resource pool, the
> > heap, when in fact there are other resource pools outside the JVM
> > that it should also concern its
Rob Clark writes:
> Here's a crazy idea: the whole problem, as I see it, arises because
> the JVM's garbage collector only knows of one resource pool, the
> heap, when in fact there are other resource pools outside the JVM
> that it should also concern itself with. [...]
>
> For example, sun could
Here's a crazy idea: the whole problem, as I see it, arises
because the JVM's garbage collector only knows of one resource pool, the
heap, when in fact there are other resource pools outside the JVM that
it should also concern itself with. Say, for example, you implement
a class, FooBar, that
I'm sorry for this intrusion,
Is there an example ( concrete to some degree ) of how to make this
happen ? ( was it posted ? )
gat
Rob Clark wrote:
> Chris Abbey wrote:
>
>> But is that memory allocated out of the chunk of VM reserved as the
>> HEAP?
>
--
Chris Abbey writes:
> So what part of garbage collection actually releases the resources
> of an object? java/lang/Object.finalize(); The way gc frees up
> resources is that it calls finalize on any object that it has
> detected is garbage (is not reachable) before it goes through and
> takes the
Rob, Michael and Nathan all have excelent points, and I agree with
every one of them; and as Linux users this is an issue that hits us
harder than most (when was the last time you saw slowaris running on
16Mb RAM? or less?); however, it shouldn't be as big an issue as it
is. (Yes, I've seen X thra
Rob Clark wrote:
>
> Chris Abbey wrote:
>
> > But is that memory allocated out of the chunk of VM reserved as the
> > HEAP?
> > I doubt it... I don't think it even blongs to the same process does
> > it?
> > Seems to me that it would have to belong to the Xserver's process...
> > in
> > the Xser
Chris Abbey wrote:
But is that memory allocated out of the chunk of
VM reserved as the HEAP?
I doubt it... I don't think it even blongs to the same process does
it?
Seems to me that it would have to belong to the Xserver's process...
in
the Xserver's address space and potentially on the Xserver's
I agree with what you said about this memory being in the X-Server. In
addition do you not get similar effects with other things in Java. For instance
when I create an File there is also a structure somewhere the keeps track of
infomation associated with the file discriptor. Also, in Windo
But is that memory allocated out of the chunk of VM reserved as the HEAP?
I doubt it... I don't think it even blongs to the same process does it?
Seems to me that it would have to belong to the Xserver's process... in
the Xserver's address space and potentially on the Xserver's machine
(as in a di
I noticed something interesting the other day, which I think would
qualify as a memory leak.
Example: create an java.awt.Image instance... the some/most of
the memory for the image is allocated under the X server process, but the
VM does not take this memory into account when deciding whether to
15 matches
Mail list logo
