On 10/30/13 4:12 PM, Robert O'Callahan wrote:
Since tasks don't share heaps, bounding their memory usage seems tractable; it becomes an accounting problem. Instead of using explicit counters I suggest following the lead of Gecko's MemShrink project and building infrastructure to compute the memory usage of a task by walking its heap.
They do though, through ARCs and RWarcs. I don't expect they're a large portion of memory usage though.
We don't have precise stack maps, though, which would be needed to have the runtime explicitly start from all stack roots and sum up all exchange heap memory in a holistic way. In the absence of that I can't think of any solution off the top of my head other than manually coded memory reporters like Gecko. But there might be something clever we can do.
Patrick _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
