Dec. 23, 2010
2:17 p.m.
Hi Paolo, On Thu, Dec 23, 2010 at 3:09 PM, Paolo Giarrusso <p.giarrusso@gmail.com> wrote:
From your description, I guess that what you describe as "raw memory" is not accounted in the stats triggering GC. That would explain the behavior you describe, and suggest an easy fix. Indeed, one could wrap the raw-memory allocator to create and update such stats; then the heap-overflow check could consider them to decide whether to trigger GC. The details of the modified heap-overflow check would probably not be entirely trivial, but still doable.
Absolutely. I will write it down in extradoc/planning/ for now. Armin