462bfeede0
When the MimeUpdateThread is done, it marks itself as finished and notifies the thread manager to clean up finished threads. Since multiple such threads might finish at the same time and trigger the cleanup notification, other threads that already marked themselves finished but haven't actually exited yet might already be deleted and removed. This would then lead to a use-after-free when they subsequently tried to send their own cleanup message. To solve the race condition, the thread manager will now wait for the thread to actually exit before cleaning it up. The introduction of the launch_daemon has made this race condition more likely due to more applications starting in parallel, each triggering a CreateAppMetaMimeThread which is a subclass of MimeUpdateThread. This commit might therefore fix #12237. |
||
---|---|---|
.. | ||
add-ons | ||
apps | ||
bin | ||
build | ||
data | ||
kits | ||
libs | ||
preferences | ||
servers | ||
system | ||
tests | ||
tools | ||
Jamfile |