New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 688535 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Add url names to url_request_context memory dumps

Project Member Reported by ssid@chromium.org, Feb 3 2017

Issue description

Background context: go/memory-infra

The url_request_context dumps just have numbers and it is hard to find why the request is made. If the url is added as an attribute it will be easy to find what's going on. It's okay if we just add domain name if not the full url.

Please keep in mind to not add this on BACKGROUND mode.

 
ssid@: are we sure that we want this? Each URLRequest is quite transient -- they come and go quickly. net/ MDP does not instrument each URLRequest. It has a "url_request_context" dump which logs the total number of requests. 

Comment 2 by ssid@chromium.org, Apr 3 2017

Ah didn't realize. I thought url_request_context is bound to a single/set of url names. The issue I was facing was I open Chrome with about:blank and see that net has some url_requests. I wanted to know why they were made in memory-infra instead of doing a net log trace. Please close this if it's not reasonable. Thanks!
Labels: -Pri-2 Pri-3
Status: Assigned (was: Untriaged)
Got it. I think for local debugging purposes, enabling "netlog" category in tracing is probably the best way to get more information. "netlog" will include all active URLRequests and their URLs. 

Lowering this to P3. I will come back after I get the long-lived allocations better instrumented :)
Status: WontFix (was: Assigned)
Closing this. I don't think we need this feature.

Sign in to add a comment