The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/255440ce6e8343609c1918c16e97885a14f9ba67

commit 255440ce6e8343609c1918c16e97885a14f9ba67
Author: jkarlin <jkarlin@chromium.org>
Date: Fri Nov 18 22:38:18 2016

Add traces to HttpCache::Transaction to make it easier to follow URLRequests

It's difficult to see how URLRequests interact on the IO thread. Adding
traces to the HttpCache::Transaction illuminates what's going on. These
traces were used to detect the performance issue in
https://crbug.com/655585 and it seems generally beneficial to keep them
in master.

BUG= 657432 

Review-Url: https://codereview.chromium.org/2432283003
Cr-Commit-Position: refs/heads/master@{#433316}

[modify] https://crrev.com/255440ce6e8343609c1918c16e97885a14f9ba67/net/cert/x509_certificate.cc
[modify] https://crrev.com/255440ce6e8343609c1918c16e97885a14f9ba67/net/http/http_cache_transaction.cc

You started fixing this bug over two years ago. Are you still working on it? You can update the status to "archived", "wontfix", or "closed". You can remove yourself as owner and change status to "untriaged", but if this is still a real bug, please do not sit on it.