From: Wincent Colaiuta Date: 2007-04-24T02:15:08+09:00 Subject: Re: Tracking down a garbage collection problem On 23 abr, 15:24, Robert Klemme wrote: > > Careful! As Guy pointed out your code basically locks cache in memory > itself. Whoops, just copied it out of the Pickaxe (p 557) without thinking. Very silly on my part, as it was only this morning that I had read a thread about lambda vs GC. I've now corrected it and am seeing the following... basically, given a bunch of calls to the parse method, the finalizer ends up getting called only some of the time... as you can see, the behavior is intermittent, so could be tricky to figure out what's going on.... will continue researching... New cache id 8678420 New cache id 10593850 New cache id 48994460 New cache id 48866440 Finalizer for id: 48866440 New cache id 80838620 New cache id 78949240 New cache id 136249000 New cache id 136172780 Finalizer for id: 136172780 New cache id 133839600 New cache id 131776570 New cache id 237020660 New cache id 237898220 New cache id 230110170 New cache id 231098300 New cache id 227400170 New cache id 226363890 New cache id 225338080 New cache id 224079680 New cache id 415597520 New cache id 416817550 Finalizer for id: 416817550 etc... Cheers, Wincent