devtools.hud.loglimit.* default limits (200) are way too few on most sites

NEW
Unassigned

Status

P2
normal
4 years ago
2 months ago

People

(Reporter: mayhemer, Unassigned)

Tracking

33 Branch
x86_64
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [polish-backlog])

(Reporter)

Description

4 years ago
Usually network requests are cut from the top on most pages I visit rendering HUD useless.

Could we raise to at least 1000 or even more?
Is this about network requests only, or about every category?

The danger is that raising the limit will slow down console rendering, but I don't have any concrete measurements. Joe or Jeff, do you have any thoughts on this? Have you by any chance been using Firefox with these limits raised?
Component: Developer Tools → Developer Tools: Console
Flags: needinfo?(jwalker)
Flags: needinfo?(jgriffiths)
(Reporter)

Comment 2

4 years ago
I think to increase this only for network requests would be enough here.
So the test site I use for this issue is: http://www.howtogeek.com/119550/browser-slow-how-to-make-mozilla-firefox-fast-again/

It makes a LOT of requests, 261 actually.

Looking at the net requests in the console, the initial html request gets cu off and there is no way to filter it or get it back. That's bad. Also, while the page is loading we get considerable jank in the tools. Also bad.

The good news is if you want to see all of the requests you can just use the network tab. That's good, but it suffers from some of the same rendering problems the console does, which is bad.

I agree this is a problem. We have a longer term plan to solve the much more serious performance / jank problem, and we have a workaround - use the netmonitor. 

Honza - is there some reason the netmonitor doesn't work for you?
Flags: needinfo?(jgriffiths) → needinfo?(honzab.moz)
(Reporter)

Comment 4

4 years ago
What is it?
Flags: needinfo?(honzab.moz)
Jeff:  Honza - is there some reason the netmonitor doesn't work for you?
Honza: > What is it?

It's the 'Network' tab, it doesn't drop requests.

I'm not against raising the limit to 1000 and seeing if we get any complaints
Flags: needinfo?(jwalker)
(Reporter)

Comment 6

4 years ago
Probably just that I cannot filer as simply as in the console and that I don't see that easily navigation changes (those are separated in the console).  Otherwise it looks good (I never used that before, tho).

Netmon renders this bug as WONTFIX or at least not a "must" for me.

Thanks!
Aren't the filter buttons at the bottom good enough?

https://developer.mozilla.org/docs/Tools/Network_Monitor#Filtering_by_content_type

The visual indication of page navigation between requests could be improved though.
(Reporter)

Comment 8

4 years ago
(In reply to Panos Astithas [:past] from comment #7)
> Aren't the filter buttons at the bottom good enough?
> 
> https://developer.mozilla.org/docs/Tools/
> Network_Monitor#Filtering_by_content_type
> 
> The visual indication of page navigation between requests could be improved
> though.

No, those are not good enough.  In the console you can filter by typing few chars of a URL.  Here I don't see anything like that.
Whiteboard: [polish-backlog]
(In reply to Joe Walker [:jwalker] (needinfo me or ping on irc) from comment #5)

> I'm not against raising the limit to 1000 and seeing if we get any complaints

Let's do this ^^
Priority: -- → P2

Updated

4 months ago
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.