https://bugs.freedesktop.org/show_bug.cgi?id=84117
Daniel Stone <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WONTFIX --- Comment #3 from Daniel Stone <[email protected]> --- 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. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ wayland-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
