Ned Konz <ned at squeakland.org> wrote:


> What I was seeing is that during recursion it got to a point where (since it 
> had built up a large count) it was never calling checkForInterrupts again.
> 
> Instead, quickCheckForInterrupts was decrementing the number by 1 each time.
> 
> Which of course never got it to 0 before all the memory was eaten.
Exactly, but...

Looking at your 21000 sends per 3mS, if we started off at 1000 (for the
reset value) then after 1000 sends, we bump reset by 10 and continue;
afte another 1010 we do it again since we're still under 3mS. And again
and again for roughly  20 times before we reach 21000 and the point at
which it ought to even out.

I'd be interested to see why it goes much beyond 21000. I'm sure it
does, since on my much slower machine it also goes pretty berserk.

Something is very odd here; even with reset clamped to 1000  and
ioProcess polling happening every 5mS (which it keeps doing all the way
to out-of-memory) I _still_ can't get an interrupt. If if do a huge
iterative loop there's no problem at all.  Have we screwed up something
in the message-send vs backward branch area?

tim
--
Tim Rowledge, tim at sumeru.stanford.edu, http://sumeru.stanford.edu/tim
Useful Latin Phrases:- Vescere bracis meis. = Eat my shorts.