- Before reproducing the problem, open a new tab and go to chrome://net-internals.
- Reproduce the network problem in a different tab. It is important to do this after opening net-internals. Keep the net-internals tab open.
- Switch back to the net-internals tab, enter some context in the text box and click "Save to file".
- Either attach the file to your existing or new bug report, or send email to the bug investigator. Include any relevant URLs or details to focus on.
- Before reproducing the problem, open a new tab and go to chrome://net-export. Press the "Start Logging to Disk" button.
- Reproduce the network problem in a different tab. It is important to do this after starting to log. Keep the net-export tab open.
- Switch back to the net-export tab. Press "Stop Logging" and then "Email Log".
- Either email the log to the bug investigator or mail it to yourself and attach the file to your existing or new bug report.
If asked to provide a byte-level capture on desktop, select "Capture" from the drop down at the top-left and check the box next to "Include the actual bytes sent/received." Do this before reproducing the network problem, between steps 1 and 2 in the instructions above.
On mobile, select “Include raw bytes” at the bottom of the page before
pressing the "Start Logging to Disk" button.
Note that captures with this level of detail may include some personal information and should generally be emailed rather than posted on public forums or bugs.
Logging on startup
If the problem that you want to log happens very early and you cannot open chrome://net-internals first, you can add a command line argument to Chrome to start logging as early as possible: