<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> <span class="fn">Daniel Stone</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Weston calls eglCreateImageKHR/eglDestroyImageKHR every frame"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84117">bug 84117</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;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Weston calls eglCreateImageKHR/eglDestroyImageKHR every frame"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84117#c3">Comment # 3</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Weston calls eglCreateImageKHR/eglDestroyImageKHR every frame"
href="https://bugs.freedesktop.org/show_bug.cgi?id=84117">bug 84117</a>
from <span class="vcard"><a class="email" href="mailto:daniel@fooishbar.org" title="Daniel Stone <daniel@fooishbar.org>"> <span class="fn">Daniel Stone</span></a>
</span></b>
<pre>No, this can't actually be fixed. Holding on to EGLImages means that the EGL
implementation can _never_ change its buffering strategy except on resize.
Doing this would actually preclude promotion to overlays in some case: imagine
you have one foreground app and one background app, both of a constant size.
Switch apps so the second is now in the foreground and can be promoted to an
overlay, if allocated from the correct backing store.
The foreground app would need to be able to release its buffers, and the
background app would need to be able to reallocate, but this is not possible if
Weston is still holding a reference to the EGLImage.
Creating and destroying images should be a very lightweight operation of
altering refcounts and adding/removing EGL resource identifiers. The buffers
themselves will _not_ be reallocated or destroyed unless the client-side EGL
(or whatever) implementation has also released its last reference to the
buffer.
If your stack is spending too long in CreateImage/DestroyImage (Vivante?), then
I'd strongly recommending your stack.</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>