From 9d65e6084c6cf81032613645c85a99529f0de38d Mon Sep 17 00:00:00 2001 From: Paul Davis Date: Sat, 16 Jan 2016 09:33:15 -0500 Subject: clean up functors used in cross-thread call_slot() messages, in case they contain shared_ptr, which could result in a dangling reference --- libs/pbd/pbd/abstract_ui.cc | 13 +++++++++++++ 1 file changed, 13 insertions(+) (limited to 'libs/pbd/pbd/abstract_ui.cc') diff --git a/libs/pbd/pbd/abstract_ui.cc b/libs/pbd/pbd/abstract_ui.cc index 65f321222e..40b4ea8d93 100644 --- a/libs/pbd/pbd/abstract_ui.cc +++ b/libs/pbd/pbd/abstract_ui.cc @@ -224,6 +224,19 @@ AbstractUI::handle_ui_requests () request_buffer_map_lock.unlock (); DEBUG_TRACE (PBD::DEBUG::AbstractUI, string_compose ("%1: valid request, calling ::do_request()\n", event_loop_name())); do_request (vec.buf[0]); + + /* if the request was CallSlot, then we need to ensure that we reset the functor in the request, in case it + * held a shared_ptr<>. Failure to do so can lead to dangling references to objects passed to PBD::Signals. + * + * Note that this method (::handle_ui_requests()) is by definition called from the event loop thread, so + * caller_is_self() is true, which means that the execution of the functor has definitely happened after + * do_request() returns and we no longer need the functor for any reason. + */ + + if (vec.buf[0]->type == CallSlot) { + vec.buf[0]->the_slot = 0; + } + request_buffer_map_lock.lock (); if (vec.buf[0]->invalidation) { DEBUG_TRACE (PBD::DEBUG::AbstractUI, string_compose ("%1: removing invalidation record for that request\n", event_loop_name())); -- cgit v1.2.3