Generally, I like the idea. Is it possible to write memory reporters for JS-implemented code? Also, is it possible to write memory reporters for Chrome Worker code?
Cheers, David On 12/17/13 4:57 AM, Nicholas Nethercote wrote: > So I want to propose something: if you're working on a change that > will introduce significant new causes of memory consumption, you > should write a memory reporter for it at the same time, rather than > (maybe) doing it later, or letting someone else do it. And in this > context, "significant" may be smaller than you expect. For example, > we have numerous reporters for things that are typically only 100s of > KBs. On B2G, 100KB per process is significant. -- David Rajchenbach-Teller, PhD Performance Team, Mozilla _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
