summaryrefslogtreecommitdiff
path: root/src/screenshooter.c
diff options
context:
space:
mode:
authorJasper St. Pierre <jstpierre@mecheye.net>2014-08-07 16:43:12 -0400
committerJason Ekstrand <jason.ekstrand@intel.com>2014-08-08 14:57:17 -0700
commitc91408f3fb7e9a98e787e9f7e370b0298083431b (patch)
tree3751f5bc1fc74f67c89632ee335442e817b3f62e /src/screenshooter.c
parent0013a29d5e8e9d25e8b3c5c6d672489ae4d7e943 (diff)
downloadweston-c91408f3fb7e9a98e787e9f7e370b0298083431b.tar.gz
Don't bother destroying resources after sending an error
An error makes the client exit, which cleans up the resources anyway. Note (Jason Ekstrand): This is safe for two reasons. First, we should be handling object destruction nicely anyway. Second, in each of these cases, the resources don't have any implementation or destruction set so it has absolutely no effect on the rest of weston whether we destroy it now or later.
Diffstat (limited to 'src/screenshooter.c')
-rw-r--r--src/screenshooter.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/src/screenshooter.c b/src/screenshooter.c
index 369e9204..9ae0d29c 100644
--- a/src/screenshooter.c
+++ b/src/screenshooter.c
@@ -265,7 +265,6 @@ bind_shooter(struct wl_client *client,
if (client != shooter->client) {
wl_resource_post_error(resource, WL_DISPLAY_ERROR_INVALID_OBJECT,
"screenshooter failed: permission denied");
- wl_resource_destroy(resource);
}
wl_resource_set_implementation(resource, &screenshooter_implementation,