Chrome's network delegate triple logs trace events |
|
Issue descriptionWith the layered network delegate chain that Chrome builds, NetworkDelegate::Notify*() ends up being called 3 times instead of just once. The concern is this means trace events are emitted 3 times. As an example, a single call to network_delegate()->NotifyStartTransaction(..) at the URLRequestJob layer will result in 3 executions of: TRACE_EVENT0(kNetTracingCategory, "NetworkDelegate::NotifyStartTransaction");
,
Jun 21 2017
Maybe those transaction starts are just really, really important! I'd tend to say we don't care about this - whenever we switch over to using a network service (Which is, admittedly, a long ways off), we'll presumably be doing things some other way, anyways, and I don't think this is a big enough issue to be worth fixing on its own, given that. |
|
►
Sign in to add a comment |
|
Comment 1 by zhongyi@chromium.org
, Jun 19 2017