>> -----Original Message-----
>> From: Marcus Crafter [mailto:[EMAIL PROTECTED]]
>> Sent: Friday, August 24, 2001 11:01 AM
>> To: [EMAIL PROTECTED]
>> Subject: RE: [C2 diff] mru store gc logging
>>
>>
>> Hi Vadim,
>>
>> On Thu, 23 Aug 2001, Vadim Gritsenko wrote:
>>
>> > BTW, what do you think about while() loop just below debug() statement?
>> > It looks to me then when this situation arises there are
>chances that storage
>> > whould be empty before GC would be kicked again...
>>
>> Seems to me like the while loop should be done before garbage
>> collection, as the loop just frees up memory, which will need to be
>> gc'd anyway. (What do you think Gerhard ?)
>
>My point here is that I am afraid that when loop is executed, it
>ALWAYS frees ALL objects from
>the cache, because freeMemory() is not changing as no GC is being
>done during loop execution.
>
>I might be not right here - I'm speaking theoretically - need to
>proof this point by experimenting.
>Additional debug() after loop with cache.size() printout would help.
In my test the cache wasn't freed totally. Most of the time he removed one
or two objects and exits the loop. but a debug statement at this point
would not be bad.
Greets from vienna
Gerhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
