<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Add new logging for network resource loading"
href="https://bugs.webkit.org/show_bug.cgi?id=162237">162237</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Add new logging for network resource loading
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>WebKit2
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>krollin@apple.com
</td>
</tr></table>
<p>
<div>
<pre>Add new logging to better track the downloading of network resources. This largely involves adding logging along the paths less travelled. The previous logging would log the normal path executed when downloading resources, but experience is showing us that this is not sufficient. Sometimes logging would suddenly stop, indicating either that some non-normal path was taken, or that the process was hung. By adding more logging, we should be able to identify the first case.
For the most part, there should be little-to-no new logging along the main path, meaning that the overall impact of our logging on the system buffers and sysdiagnose should be minimal.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>