442648edc0
Otherwise it's theoretically possible to create a new ClientConnection object for the zombie wl_client when its resources are being destroyed. For example - process early wl_client destroy notification - the ClientConnection objects gets removed from the client list in Display - process wl_resource objects getting destroyed - if some code calls display->getConnection(zombie_client), it's going to reintroduce the client in the client list - process late wl_client destroy notification, it's going to destroy the original and the clone ClientConnection object This change prevents reintoducing a clone client object, by keeping the original for a bit longer until it's actually destroyed. In the future though, it would be great to kill the client lists in Display and ClientConnection, and just use `static_cast<ClientConnection *>(wl_client_get_user_data())`. |
||
---|---|---|
.. | ||
CMakeLists.txt | ||
test_datacontrol_interface.cpp | ||
test_display.cpp | ||
test_inputmethod_interface.cpp | ||
test_keyboard_shortcuts_inhibitor_interface.cpp | ||
test_layershellv1_interface.cpp | ||
test_no_xdg_runtime_dir.cpp | ||
test_screencast.cpp | ||
test_seat.cpp | ||
test_tablet_interface.cpp | ||
test_textinputv1_interface.cpp | ||
test_textinputv3_interface.cpp | ||
test_viewporter_interface.cpp |