On Fri, Dec 20, 2013 at 8:07 PM, Terrence Cole <[email protected]> wrote:
> On 12/20/2013 06:24 AM, Julien Wajsberg wrote: > > * have diagnostics about what happens in the memory and other GC-related > > stuff > > + know when a GC happens (see below for the Profiler) > > + have a tool that shows the memory consumption over time (à la > > jconsole, cf [1], or visualvm [2]) > > I'm also sad that we haven't gotten something like this hooked up yet. > For now I'd recommend the excellent extension memchaser[1]. If you need > more detail you can turn on javascript.options.mem.log in about:config > and look at individual GC's in your browser console. > > 1 - https://addons.mozilla.org/en-US/firefox/addon/memchaser/ > We will have a lot of interesting things to say about memory tools in 2014, but in the meantime you may also find this prototype add-on useful: https://github.com/past/memory-profiler _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
