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 SpiderMonkey Debugger API ha
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 Je
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 way
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
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, t
>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 ski
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 suc
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 de
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
k
>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 performa
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
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
>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
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 - but that doesn't really ca
[Note: I'm a tab-hoarder - but that doesn't really cause this problem]
tl;dr: we should look at something (roughly) like the existing "page is
making your browser slow" dialog for website leaks.
Over the last several months (and maybe the last year), I've noticed an
increasing problem in website
15 matches
Mail list logo
