We have https://bugzilla.mozilla.org/show_bug.cgi?id=1243091 on file for automatic leak detection in the DevTools' memory panel.
I'd have liked to try implementing http://www.cs.utexas.edu/ftp/techreports/tr06-07.pdf because it can see through frameworks/libraries (or claims to in a convincing way, at least) and point to the "user" code that is transitively responsible. In today's modern web that is full of every kind of framework and library, that seems like a very useful property to have. As far as seeing the CC's heap, there is https://bugzilla.mozilla.org/show_bug.cgi?id=1057057 on file for that. It shouldn't be hard for someone who understand the CC and all of its macros. You basically just make a specialization of JS::ubi::Concrete that can enumerate outgoing edges and report shallow size. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
