threads. Its memory resources (such as the stack) are not freed until it is reaped by another thread. In
contrast, a detached thread cannot be reaped or killed by other threads. Its memory resources are freed
automatically by the system when it terminates.
By default, threads are created joinable. In order to avoid memory leaks, each joinable thread should either
be explicitly reaped by another thread, or detached by a call to the pthread detach function.
#include <pthread.h>
int pthread_detach(pthread t tid);
returns: 0 if OK, non-zero on error
The pthread detach function detaches the joinable thread tid. Threads can detach themselves by
calling pthread detach with an argument of pthread self().
Even though some of our examples will use joinable threads, there are good reasons to use detached threads
in real programs. For example, a high-performance Web server might create a new peer thread each time
it receives a connection request from a Web browser. Since each connection is handled independently by a
separate thread, it is unnecessary and indeed undesirable for the server to explicitly wait for each peer thread
to terminate. In this case, each peer thread should detach itself before it begins processing the request so
that its memory resources can be reclaimed after it terminates.
摘自《深入理解计算机系统》
本文详细阐述了计算机系统中线程的两种状态:可连接和可分离。解释了可连接线程如何通过其他线程进行回收和终止,以及其内存资源直到被另一个线程回收才释放。相比之下,可分离线程在终止时由系统自动释放内存资源,无需其他线程干预。默认情况下,线程创建为可连接,为避免内存泄漏,应明确通过调用pthreads detach函数进行回收或使其成为可分离线程。
1万+

被折叠的 条评论
为什么被折叠?



