<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:bburg@apple.com" title="Brian Burg <bburg@apple.com>"> <span class="fn">Brian Burg</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: type profiler does not dim functions that were never called"
href="https://bugs.webkit.org/show_bug.cgi?id=140962">bug 140962</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>bburg@apple.com
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: type profiler does not dim functions that were never called"
href="https://bugs.webkit.org/show_bug.cgi?id=140962#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Web Inspector: type profiler does not dim functions that were never called"
href="https://bugs.webkit.org/show_bug.cgi?id=140962">bug 140962</a>
from <span class="vcard"><a class="email" href="mailto:bburg@apple.com" title="Brian Burg <bburg@apple.com>"> <span class="fn">Brian Burg</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=140962#c3">comment #3</a>)
<span class="quote">> The problem here is that when the inspector first opens with type profiling
> enabled (or the user turns type profiling on mid-way through inspection),
> JavaScriptCore has an incomplete view of those functions that have run and
> those functions that have not run. Because of this, JavaScriptCore won't get
> completely accurate information until the page is refreshed.
>
> The approach to this problem is two fold:
>
> 1. We're going to switch the default to be from assuming a function has run
> to assuming it has not run. This doesn't solve the problem, but it is less
> misleading and probably a better default.
>
> 2. We're removing gray backgrounds of unexecuted basic blocks and instead
> are going to lessen the saturation of the syntax highlighting on these
> unexecuted blocks. Again, this doesn't solve the problem, but provides a
> more subtle UI that is less obviously misleading. It is also more pleasant
> to use.
>
> In the future, we can solve this more directly by at least considering
> enabling JavaScriptCore's /runtime/FunctionHasExecutedCache class to be
> enabled at all time and not only when the type profiler or control flow
> profiler is enabled.</span >
What's the state of this bug today, Saam?</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>