1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

thread.c (thread_cleanup_func): document small leak

Browse Source 
It's minor, I haven't analyzed how fixable it is, but we should
at least note it, here.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@61779 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
This commit is contained in:
normal 2018-01-12 00:15:28 +00:00
parent afe296be78
commit 99886a9121
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
thread.c
View File

@ -554,6 +554,10 @@ thread_cleanup_func(void *th_ptr, int atfork)
* Unfortunately, we can't release native threading resource at fork * Unfortunately, we can't release native threading resource at fork
* because libc may have unstable locking state therefore touching * because libc may have unstable locking state therefore touching
* a threading resource may cause a deadlock. * a threading resource may cause a deadlock.
*
* FIXME: Skipping native_mutex_destroy(pthread_mutex_destroy) is safe
* with NPTL, but native_thread_destroy calls pthread_cond_destroy
* which calls free(3), so there is a small memory leak atfork, here.
*/ */
if (atfork) if (atfork)
return; return;