renderer: Seperate info's lifecycle from client 95/317095/1
authorTaeHyeon Jeong <thyeon.jeong@samsung.com>
Wed, 4 Sep 2024 01:33:31 +0000 (10:33 +0900)
committerTaeHyeon Jeong <thyeon.jeong@samsung.com>
Wed, 4 Sep 2024 02:54:48 +0000 (11:54 +0900)
AS-IS
- when the renderer_client is removed, the info is also erased

TO-BE
- regardless of the renderer_client's destruction, the info is maintained

Change-Id: I4af548b3f1c71b06183b09882095705fac31bb82

src/renderer/renderer.c

index 18848d2..62e6869 100644 (file)
@@ -282,8 +282,8 @@ _tizen_renderer_client_handle_destroy(struct wl_resource *resource)
     ds_inf("_tizen_renderer_client_handle_destroy (client:%p)", client);
 
     wl_list_for_each_safe(info, tmp, &client->infos, link) {
-        wl_signal_emit(&info->events.destroy, info);
-        wl_resource_destroy(info->resource);
+        info->client = NULL;
+        wl_list_remove(&info->link);
     }
 
     wl_list_remove(&client->link);