Re: Website memory leaks

2017-11-06 Thread Nick Fitzgerald
On Mon, Nov 6, 2017 at 1:53 AM, David Teller wrote: > I wanted to add something like that to about:performance, but at the > time, my impression was that we did not have sufficient platform data on > where allocations come from to provide something convincing. > ​The

Re: Website memory leaks

2017-11-06 Thread David Teller
As a user, I would definitely love to have this. I wanted to add something like that to about:performance, but at the time, my impression was that we did not have sufficient platform data on where allocations come from to provide something convincing. Cheers, David On 02/11/17 15:34, Randell

Re: Website memory leaks

2017-11-02 Thread Nick Fitzgerald
We have https://bugzilla.mozilla.org/show_bug.cgi?id=1243091 on file for automatic leak detection in the DevTools' memory panel. I'd have liked to try implementing http://www.cs.utexas.edu/ftp/techreports/tr06-07.pdf because it can see through frameworks/libraries (or claims to in a convincing

Re: Website memory leaks

2017-11-02 Thread Robert O'Callahan
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

Re: Website memory leaks

2017-11-02 Thread smaug
On 11/02/2017 09:58 PM, Kris Maglione wrote: Related: I've been thinking for a long time that we need better tools for tracking what sites/usage patterns are responsible for the time we spend in CC (and possibly GC, but I think that tends to be less of a problem). I've noticed, in particular,

Re: Website memory leaks

2017-11-02 Thread Randell Jesup
>On Thu, Nov 02, 2017 at 05:37:30PM +0200, smaug wrote: >>This has been an issue forever, and there aren't really good tools on any >>browser, as far as >>I know, for web devs to debug their leaks. >>Internally we do have useful data (CC and GC graphs and such), but would need >>quite some ux

Re: Website memory leaks

2017-11-02 Thread smaug
On 11/02/2017 10:01 PM, Kris Maglione wrote: On Thu, Nov 02, 2017 at 05:37:30PM +0200, smaug wrote: This has been an issue forever, and there aren't really good tools on any browser, as far as I know, for web devs to debug their leaks. Internally we do have useful data (CC and GC graphs and

Re: Website memory leaks

2017-11-02 Thread Kris Maglione
On Thu, Nov 02, 2017 at 05:37:30PM +0200, smaug wrote: This has been an issue forever, and there aren't really good tools on any browser, as far as I know, for web devs to debug their leaks. Internally we do have useful data (CC and GC graphs and such), but would need quite some ux skills to

Re: Website memory leaks

2017-11-02 Thread Kris Maglione
Related: I've been thinking for a long time that we need better tools for tracking what sites/usage patterns are responsible for the time we spend in CC (and possibly GC, but I think that tends to be less of a problem). I've noticed, in particular, that having multiple Amazon tabs open, and

Re: Website memory leaks

2017-11-02 Thread Randell Jesup
>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

Re: Website memory leaks

2017-11-02 Thread David Durst
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

Re: Website memory leaks

2017-11-02 Thread smaug
This has been an issue forever, and there aren't really good tools on any browser, as far as I know, for web devs to debug their leaks. Internally we do have useful data (CC and GC graphs and such), but would need quite some ux skills to design some good UI to deal with leaks. Also, the data to

Re: Website memory leaks

2017-11-02 Thread Randell Jesup
>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

Re: Website memory leaks

2017-11-02 Thread Shih-Chiang Chien
about:performance can provide the tab/pid mapping, with some performance indexes. This might help solve your issue listed in the side note. Best Regards, Shih-Chiang Chien Mozilla Taiwan On Thu, Nov 2, 2017 at 3:34 PM, Randell Jesup wrote: > [Note: I'm a tab-hoarder -