Mark thread name setup safe for nodes

This commit is contained in:
Pedro J. Estébanez 2023-06-07 19:40:30 +02:00
parent 828ec2c5d0
commit 543689eeed
1 changed files with 4 additions and 0 deletions

View File

@ -1187,7 +1187,11 @@ void Thread::_start_func(void *ud) {
ERR_FAIL_MSG(vformat("Could not call function '%s' on previously freed instance to start thread %s.", t->target_callable.get_method(), t->get_id())); ERR_FAIL_MSG(vformat("Could not call function '%s' on previously freed instance to start thread %s.", t->target_callable.get_method(), t->get_id()));
} }
// Finding out a suitable name for the thread can involve querying a node, if the target is one.
// We know this is safe (unless the user is causing life cycle race conditions, which would be a bug on their part).
set_current_thread_safe_for_nodes(true);
String func_name = t->target_callable.is_custom() ? t->target_callable.get_custom()->get_as_text() : String(t->target_callable.get_method()); String func_name = t->target_callable.is_custom() ? t->target_callable.get_custom()->get_as_text() : String(t->target_callable.get_method());
set_current_thread_safe_for_nodes(false);
::Thread::set_name(func_name); ::Thread::set_name(func_name);
// To avoid a circular reference between the thread and the script which can possibly contain a reference // To avoid a circular reference between the thread and the script which can possibly contain a reference