>Many of the pages causing these leaks are major sites, like nytimes.com, >washington post, cnn, arstechnica, Atlantic, New Yorker, etc. ... >Perhaps we can also push to limit memory use (CPU use??) in embedded >ads/restricted-iframes/etc, so sites can stop ads from destroying the >website performance for users over time. I've often seen ads taking >300MB-2GB.
So in support of this general concept of limiting ad memory use: https://www.scientificamerican.com/article/should-iconic-lake-powell-be-drained/ doesn't leak if you load it -- until you scroll down, and the ads load. Then it leaks forever... to the tune of 1GB leaked in 5-10 minutes. Differential about:memory reports show that what's primarily leaking are ads, in particular at this moment: 400.25 MB (43.45%) -- detached 398.81 MB (43.30%) -- window(https://tpc.googlesyndication.com/safeframe/1-0-13/html/container.html) seems like the worst culprit, plus 406.69 MB (44.15%) -- top(https://www.scientificamerican.com/article/should-iconic-lake-powell-be-drained/,id=NNN) 327.79 MB (35.59%) -- js-zone(0xNNN) Other ads have leaked a few MB to 75MB each. Also, as soon as I scrolled down CPU use went from ~0% for the process to ~20% (on a 4-thread/core AMD CPU). Worse yet (perhaps bug 1410381??) when I hit reload CPU use dropped (not to 0). 10 sec later, Mem use climbed 3.7GB to 4.5GB. then dropped to 3.7GB and climbed back to 4.5GB. Then dropped to 2.7GB - barely above where it was before I scrolled down - and stayed stable. (Note: I hit reload with the current position near the bottom with 1 ad visible (no video). Using an additional GB+ of memory in order to free 1GB of memory seems... excessive. -- 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
