What you're describing having seen is, I think, exactly what I've been trying to reproduce in a now-blocking-57 bug (1398652).
By your description, the only thing that makes sense to me -- to account for unknown/unknowable changes on the site -- is to track potential runaway growth of the content process. I realize how stupid this sounds, but what I observed was that when the content process was in trouble, it continued to grow. And the effect/impact builds: first the tab, then the process, then the browser, then the OS. So if there's a way to determine that "this process has only grown in the past X amount of time" or past a certain threshold, that's the best indicator I've come up with. I don't know what we'd do at that point -- force killing the content process sounds severe (though possibly correct) -- or some alert similar to the dreaded slow script one. -- David Durst [:ddurst] On Thu, Nov 2, 2017 at 11:31 AM, Randell Jesup <rjesup.n...@jesup.org> wrote: > >about:performance can provide the tab/pid mapping, with some performance > >indexes. > >This might help solve your issue listed in the side note. > > mconley told me in IRC that today's nightly has brought back the PID in > the tooltip (in Nightly only); it was accidentally removed. > > about:performance can be useful, but 3 tabs vs all tabs is too coarse > for me, and things like "site leaked memory and is slowing CC" I presume > doesn't show up in the 'heat' for the tab there. > > -- > Randell Jesup, Mozilla Corp > remove "news" for personal email > _______________________________________________ > 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
