Hello Craig,

On 14.02.2006 22:07, Craig Latta wrote:
> Hi--
> 
> 	I have a variant of the garbage collector working, one which doesn't 
> mark methods which haven't been run recently. This does most of the work 
> of shrinking an object memory, in one fell swoop (and it runs at full 
> speed). Now I just kill unwanted processes from afar, clear all method 
> activation marks, run a few things I know I'll want (mostly support for 
> remote messaging), then make a snapshot. The automatic removal of unrun 
> methods this way causes a chain reaction, with the freeing of unused 
> method literals.
> 

> 	What used to take days (shrinking manually with a remote system 
> browser) now takes a couple of seconds.

This sounds great!

But what happens if there arises an Exception after shrinking the system
which not has arosen before?


Regards,
Stephan

> 
> 
> -C
> 

-- 
Stephan Rudlof (sr at evolgo.de)
   "Genius doesn't work on an assembly line basis.
    You can't simply say, 'Today I will be brilliant.'"
    -- Kirk, "The Ultimate Computer", stardate 4731.3