🚀 go-pugleaf

System.gc() doesn't call the garbage collector.  It's a request that may
be, at some point in the near to distant future be considered for
possibly convincing the garbage collector to fire if it wants to.

-Rich

Captain Claw wrote:
> Try giving System.gc() ocassionally to invoke the garbage collector
>
>
> Rich Wilkman wrote:
>
>> Xuegang Ban:
>>
>> Is it being 'eaten' or is it just null and waiting for the garbage
>> collector to
>> come get it?  Just using the system tools in NT won't tell you much
>> that you
>> need to diagnose this.  To me, it sounds like each loop does 5M
>> worth of work
>> with no object re-use.  If the garbage collector can fire before you
>> run out of
>> memory, you'll get back the dead references.  Your NT monitors,
>> however, won't
>> show you that; it'll just show you the total heap size.
>>
>> -Rich
>>
>> banxuegang wrote:
>>
>> > Hi,
>> > I used Thread class in my Java Application. There is a loop in it.
>> But, I
>> > found that every time this loop execuates, the system memory is
>> eaten by 5
>> > MB. What's the problem? I think there are should not Memory
>> problems in Java
>> > Programming. But....
>> > Thanks.
>> >
>> > --
>> > Xuegang Ban
>> > Civil&Enviromental Engineering Department,
>> > Univ. of Wisconsin-Madison
>> > Email: ban@cae.wisc.edu
>> > Phone: 608-262-3967(o)
>> >             608-260-9123(h)
>