Re: [MIT-Scheme-devel] Cleaning weak hash tables in secondary GC daemon?

[Matt Birkholz]

> From: Matt Birkholz <address@hidden>
> Date: Tue, 20 Sep 2011 16:38:07 -0700
> 
> > From: Taylor R Campbell <address@hidden>
> > Date: Tue, 20 Sep 2011 21:47:50 +0000
> > 
> >    Date: Tue, 20 Sep 2011 14:21:22 -0700
> >    From: Matt Birkholz <address@hidden>
> > 
> >    I find trigger-secondary-gc-daemons! is called only in gc-clean,
> >    which is called only in runtime/make.scm and disk-save.
> > 
> > GC-FINISH also calls GC-CLEAN when there are fewer than 4096 words
> > remaining in the heap after garbage collection.  When this happens,
> > Scheme will abort to the nearest REPL and exclaim `out of memory!'.
> 
> Sorry, somehow I missed that twice.  So I do not need to call
> trigger-secondary-gc-daemons!  Thanks.  I must have hit "Aborting!:
> out of memory" for other reasons.  I will have to let a GtkLayout demo
> run down to 4Kwords just to see it go.

Hang on.  It does BOTH?  Can we try an abort SECOND?  I was running a
demo for two days, then poof!  I thought me program had exploded
(again), but now it seems me program was exploded by the deux in le
machine just because it needed a little tender loving
trigger-secondary-gc-daemons! one time.

I think I'll leave my own trigger- in there.  Flipping all that WTF
back and forth with my generation0 seems like a lose.  Heck, I could
trigger-secondary-gc-daemons! HOURLY... ON the hour, with a little
gumption.