This touches on a really important point: we're not the only ones allocating memory.
Just a few that come to mind: GPU drivers, system media codecs, a11y tools, and especially on Windows we have to deal with "utility" applications, corporate-mandated gunk, and downright crapware. When we're measuring progress toward our goals, look at not only your own pristine dev box but also that one neighbor whose adware you're always cleaning out. On Fri, Jul 13, 2018 at 7:57 AM Gabriele Svelto <gsve...@mozilla.com> wrote: > > Just another bit of info to raise awareness on a thorny issue we have to > face if we want to significantly raise the number of content processes. > On 64-bit Windows we often consume significantly more commit space than > physical memory. This consumption is currently unaccounted for in > about:memory though I've seen hints of it being cause by the GPU driver > (or other parts of the graphics pipeline). I've filed bug 1475518 [1] so > that I don't forget and I encourage anybody with Windows experience to > have a look because it's something we _need_ to solve to reduce content > process memory usage. > > Gabriele > > [1] Commit-space usage investigation > https://bugzilla.mozilla.org/show_bug.cgi?id=1475518 > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
