I wrote:
> I think the original unsigned + underflow avoidance code
> prevented us from accounting free() properly, and we were
> triggering GC more as a result.

(Warning: thinking out loud while sleep-deprived)

What's dangerous about this patch correcting the
free()-before-malloc() accounting is that it not only breaks
expectations with our current malloc limits; everybody who sets
custom limits in env also gets things broken.

So, I'm not sure what to do about it...

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>