<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 - [GTK] Implement rendering frames timeline panel for GTK+ port"
href="https://bugs.webkit.org/show_bug.cgi?id=150392">150392</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[GTK] Implement rendering frames timeline panel for GTK+ port
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Local 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>Keywords</th>
<td>Gtk
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>Web Inspector
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>cgarcia@igalia.com
</td>
</tr>
<tr>
<th>CC</th>
<td>bburg@apple.com, gns@gnome.org, graouts@webkit.org, joepeck@webkit.org, mattbaker@apple.com, nvasilyev@apple.com, timothy@apple.com, webkit-bug-importer@group.apple.com, zan@falconsigh.net
</td>
</tr></table>
<p>
<div>
<pre>The Web Inspector has now a nice view to show the rendering times when in accelerated compositing mode, but that doesn't work in GTK+. It's quite confusing for the users, because the panel is in the inspector but it is never updated. This is because we don't implement the instrumentation required. The mac implementation is based on RunLoopObserver, that only has an implementation based on CF. It's not currently possible to do the same with the glib main loop, so even if there's a proper platform abstraction of RunLoopObserver, we won't be able to provide a glib implementation. Maybe when persistent sources patch lands (see <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Add persistent GSource wrapper"
href="show_bug.cgi?id=138691">bug #138691</a>), we can provide a way to monitor our sources. For now, what we can do is to use a custom persistent source for the AC rendering, instead of a GMainLoopSource and notify the inspector on every source dispatch, after and before actually dispatching the source callback. And it will improve the performance for the same price.</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>