Re: Controlling the Garbage Collector

From:

Eric Sosman <esosman@ieee-dot-org.invalid>

Newsgroups:

comp.lang.java.programmer

Date:

Mon, 25 Jun 2012 13:45:03 -0400

Message-ID:

<jsa838$vih$1@dont-email.me>

On 6/25/2012 1:01 PM, Andreas Leitgeb wrote:

Eric Sosman <esosman@ieee-dot-org.invalid> wrote:

On 6/25/2012 8:28 AM, Jukka Lahtinen wrote:

Robert Klemme <shortcutter@googlemail.com> writes:

Long lived objects which live shorter than the application (i.e. not
classes) are actually the Achilles heel of GC because it is very hard to
tune the collector in a way that it does not visit those long living
objects too often and yet run often enough to ensure enough free memory is

It might be good to have a method to gell the GC that a certain
long-lived object is no longer needed.
For example, something like
System.gc(Object old)
where old is the object that has just been needed the last time.

How would you call the method?

class MyRef<T> {
    private T ref;
    public T consume() { T tmp = ref; ref=null; return tmp; }
    public MyRef(T t) { ref=t; }
}
[...somewhere else...]
    BigObject bo=new BigObject();
    // use bo ...
    MyRef<BigObject> mrBo = new MyRef<>(bo); bo=null;
    System.gc( mrBo.consume() );
;-)

;-)

Maybe slightly more interesting questions:
What would be the behaviour of that proposed call,
- if "old" *is* still (hard-)referenced from live objects?
- if there's still a weak/soft-reference on that object?
(pick one: Exception, force(for weak/soft-refs) or ignore?)

Exactly: The JVM could not simply trust the System.gc(obj)
call to be telling the truth, because that would open the door
to all manner of attacks. Therefore the JVM would have to verify
that obj was unreachable (at whatever strength) before deciding
to dispose of it. That is, the JVM would have to run nearly all
of the garbage collector to determine obj's reachability -- so
why not just run the ordinary GC in the ordinary way? I'm at a
loss to imagine what benefit a System.gc(obj) would offer.

--
Eric Sosman
esosman@ieee-dot-org.invalid