New issue
Advanced search Search tips

Issue 740280 link

Starred by 0 users

Issue metadata

Status: Untriaged
Owner: ----
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Devtools console spew makes logging almost unusable

Project Member Reported by brettw@chromium.org, Jul 7 2017

Issue description

Starting a debug version of Chrome on Linux produces 1172 lines of output. Most of this is is mirroring devtools console to the native Chrome logging system (via RenderFrameHostImpl::OnDidAddMessageToConsole).

On Google corp machines, this includes the full 1120-line PAC file.

This level of spew makes the entire logging system almost unusable.
 
Components: Platform>DevTools
Components: -Platform>DevTools
Owner: brettw@chromium.org
Status: Assigned (was: Untriaged)
- I did not put this code there, but I don't think we care much about the debug version output on the corp machines
- logging full 1120-line PAC files will also cache (effectively memory leak) it since console unconditionally caches 100 messages for post-factum debugging. do you want to follow up with them to not do it?

Comment 3 by brettw@chromium.org, Mar 20 2018

Owner: ----
Status: Available (was: Assigned)
Status: Untriaged (was: Available)
Available, but no owner or component? Please find a component, as no one will ever find this without one.

Sign in to add a comment