LadybirdBrowser/ladybird
1
1
Fork 0
mirror of https://github.com/LadybirdBrowser/ladybird.git synced 2024-09-20 01:37:39 +03:00
Code Issues Packages Projects Releases Wiki Activity

LibThread: Fix destroying background actions

Browse Source 
In the old model, before bc319d9e88, the parent
(the background thread) would delete us when it exits (i.e. never), so we had to
keep track of our own refcount in order to destroy ourselves when we're done.

With bc319d9e88, the parent keeps additional
reference to us, so:
* There should be no need to explicitly ref() ourselves
* The unref() would not get rid of the last reference to us anymore

The latter is why all the BackgroundAction's were getting leaked. Fix this by
simply unparenting ourselves from the background thread when we're done.
This commit is contained in:
Sergey Bugaev 2020-02-25 12:05:25 +03:00 committed by Andreas Kling
parent ab9a0780e3
commit cbf2881bf7
Notes: sideshowbarker 2024-07-19 09:04:41 +09:00 
Author: https://github.com/bugaevc
Commit: https://github.com/SerenityOS/serenity/commit/cbf2881bf71
Pull-request: https://github.com/SerenityOS/serenity/pull/1292
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Libraries/LibThread/BackgroundAction.h
View File

@ -75,17 +75,17 @@ private:
{
LOCKER(all_actions().lock());
this->ref();
all_actions().resource().enqueue([this] {
m_result = m_action();
if (m_on_complete) {
Core::EventLoop::current().post_event(*this, make<Core::DeferredInvocationEvent>([this](auto&) {
m_on_complete(m_result.release_value());
this->unref();
this->remove_from_parent();
}));
Core::EventLoop::wake();
} else
this->unref();
} else {
this->remove_from_parent();
}
});
}