From 92e65ba3c790c68b9d709330582257fcd0173870 Mon Sep 17 00:00:00 2001 From: Derek Foreman Date: Wed, 26 Apr 2017 14:16:37 -0500 Subject: [PATCH] wayland_shm: Stop using the evas directly to block for async render Use the new fence function instead. This makes Cedric less unhappy. --- src/modules/evas/engines/wayland_shm/evas_dmabuf.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/src/modules/evas/engines/wayland_shm/evas_dmabuf.c b/src/modules/evas/engines/wayland_shm/evas_dmabuf.c index 4f165d1..92413ea 100644 --- a/src/modules/evas/engines/wayland_shm/evas_dmabuf.c +++ b/src/modules/evas/engines/wayland_shm/evas_dmabuf.c @@ -413,7 +413,6 @@ static const struct wl_buffer_listener buffer_listener = static void _fallback(Dmabuf_Surface *s, int w, int h) { - Evas_Public_Data *epd; Dmabuf_Buffer *b; Surface *surf; Eina_Bool recovered; @@ -446,8 +445,7 @@ _fallback(Dmabuf_Surface *s, int w, int h) if (!b->mapping) goto out; - epd = efl_data_scope_get(surf->info->evas, EVAS_CANVAS_CLASS); - while (epd && epd->rendering) evas_async_events_process_blocking(); + evas_thread_queue_wait(); old_data = b->mapping; surf->funcs.assign(surf); -- 2.7.4