Now that I'm writing a Web app for real, I realize just how easy it is to accidentally leak :-(.
It would be useful, or at least cool, to be able to show users and developers a graph of memory usage over time, one line per tab. You could limit this to just show the top N memory-hungry tabs. A UI intervention like the slow-script notification seems plausible. You can probably come up with pretty good heuristics for identifying leaking tabs. One signal would be steady memory growth during times without user interaction. Then you can show the memory growth graph and offer to reload the tab. When devtools are open you could be a lot more aggressive about warning developers if you think their app might be leaking. Actually, as an aside, there's a more general devtools request here: when I'm using my own app, even when devtools are not open, I'd like to be notified of JS errors and other serious issues. One way to do this would be that if I ever open devtools on a site, then set a "warn on errors" flag for that site, and ensure the warnings offer a "stop warning me" button. There's a lot of research literature on tools for tracking down leaks using periodic heap snapshots and other techniques. Most of it's probably junk but it's worth consulting. Nick Mitchell and Gary Sevitsky did some good work. IIRC you already have a "this is probably an ad" URL blacklist, so bounding the memory usage of those IFRAMEs, freezing them when they reach it, sounds good. You shouldn't need process isolation for IFRAMEs for this. Rob -- lbir ye,ea yer.tnietoehr rdn rdsme,anea lurpr edna e hnysnenh hhe uresyf toD selthor stor edna siewaoeodm or v sstvr esBa kbvted,t rdsme,aoreseoouoto o l euetiuruewFa kbn e hnystoivateweh uresyf tulsa rehr rdm or rnea lurpr .a war hsrer holsa rodvted,t nenh hneireseoouot.tniesiewaoeivatewt sstvr esn _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
