From 31e280c147fb1692f4936931bbf34cb46e54ccb4 Mon Sep 17 00:00:00 2001 From: Daniel van Vugt Date: Wed, 7 Aug 2024 15:30:37 +0800 Subject: [PATCH] onscreen/native: Don't release the dumb buffers on successful zero-copy Because a zero-copy import might fail later for driver or resource reasons. So we may still need the dumb buffers as a fallback. Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/3606 Part-of: --- src/backends/native/meta-onscreen-native.c | 6 ------ 1 file changed, 6 deletions(-) diff --git a/src/backends/native/meta-onscreen-native.c b/src/backends/native/meta-onscreen-native.c index 552ea11f7..c118dde72 100644 --- a/src/backends/native/meta-onscreen-native.c +++ b/src/backends/native/meta-onscreen-native.c @@ -822,12 +822,6 @@ import_shared_framebuffer (CoglOnscreen *onscreen, if (secondary_gpu_state->import_status == META_SHARED_FRAMEBUFFER_IMPORT_STATUS_NONE) { - /* - * Clean up the cpu-copy part of - * init_secondary_gpu_state_cpu_copy_mode () - */ - secondary_gpu_release_dumb (secondary_gpu_state); - meta_topic (META_DEBUG_KMS, "Using zero-copy for %s succeeded once.", meta_render_device_get_name (render_device));