On Mon, Feb 23, 2015 at 01:13:02AM -0800, Nicholas Nethercote wrote: > On Sun, Feb 22, 2015 at 10:46 PM, Mike Hommey <m...@glandium.org> wrote: > >> > >> We've had increasing numbers of cases lately on Windows where memory > >> usage goes out of control but the existing memory reporters (e.g. the > >> "explicit" tree in about:memory) doesn't show anything. This is > >> because the memory usage is related to gfx and/or video playing and so > >> comes from the graphics driver or something similar. This new reporter > >> is an attempt to get some insight into such cases, though it's still > >> fairly crude. If anybody else has any ideas on additional measurements > >> that could prove helpful for these kinds of cases, please let me know. > >> Thank you. > > > > Note that bug 1134565 and related bugs I'm going to file soon are > > possibly related too. > > Oh, right, because all heap memory allocated by Angle was > (accidentally) using the system heap which doesn't get reported in > about:memory. Great, thank you for fixing.
So, it turns out we're lucky... while Angle and others are not using the wrappers for operator new, they still end up using our version of operator new that calls moz_xmalloc somehow (call that luck if you will) Mike _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
