How to get data for bug reports

1. Reproduce the network problem.
2. Click the Dump to file button in the Export tab.
3. The log file will act like a normal download.
4. Email this log file to the bug investigator, along with an explanation of what went wrong, including any relevant URLs. You may want to compress the file before sending, as the log files can be fairly large but compress well.

• The network log may contain personally identifying information like IP addresses, URLs, and cookies.
• You can edit the log to obscure information if you like, but sometimes it is relevant to the bug. If you choose do this, please make sure you can still load the log file.
• If you choose not to have cookies removed from the log, you must toggle the checkbox before clicking the button.
• Ideally you would have the tool running before you reproduce the bug. If that isn't possible (perhaps the bug happens unpredictably), then the next best thing is to load chrome://net-internals/ as soon as you can after the problem has occurred.

How it works

• While the net-internals page is open, it will capture the network events that are happening in Chrome. You can view that in real-time by going to the Events tab.
• Once you close the net-internals window, the data it had captured will be discarded.
• Chrome keeps around a small buffer of the most recent network events even when the net-internals window is not open. That way if you open chrome://net-internals/ shortly after encountering a problem, you may still find the relevant data. These passively captured events are less accurate however, and will be prefixed in the log with (P).

Close this popup