New issue
Advanced search Search tips

Issue 659666 link

Starred by 2 users
Status: WontFix
Owner:
dproy@chromium.org
Closed: Oct 17
Cc:
caseq@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: ----
Type: ----



Sign in to add a comment

Delete old networking trace events once Networking Tracing v2 is good enough

Project Member Reported by dproy@chromium.org, Oct 26 2016 
We're building the next generation of network instrumentation in chrome that should enable us to track the life of a network request more faithfully throughout the different stacks. Once the new network instrumentation coverage is good enough, the old trace events that tracked various network events should be removed.


Design doc: https://docs.google.com/document/d/1s0DKjNJk85hDuRp5IqujwZvPML-MPsyAtDeksMwBw7s/edit

Comment 1 by chiniforooshan@chromium.org, Aug 14 2017

Cc: -chiniforooshan@chromium.org

Comment 2 by falken@chromium.org, Oct 17 

I just ran across the following:

  // TODO(dproy): Remove this.  http://crbug.com/659666 
  TRACE_EVENT1("blink", "ResourceFetcher::requestResource", "url",
               UrlForTraceEvent(params.Url()));

What's the status of this bug?

Comment 3 by dproy@chromium.org, Oct 17

Status: WontFix (was: Assigned)
This project was deprioritized and currently there are no owners. Looks like this trace event is still used by catapult [0], so it's best to keep this event.

Marking this bug as WontFix, and I'll send a CL to remove the TODO. 

[0] https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/extras/chrome/chrome_user_friendly_category_driver.html?l=159&rcl=b273e0cd217d87f33caacb8ed15d85801fcca9ea
►

Sign in to add a comment