C++中如何避免分离线程（detach）引发的内存泄漏？

问题重现 #

你的代码中，foo3()创建两个线程后调用detach()，主线程直接退出，Valgrind检测到"possibly lost"的内存块，对应线程TLS（线程本地存储）相关的分配：

#include <iostream>
#include <vector>
#include <thread>
class student{
    public: 
        std::string name;
        int id;
};
void foo(){
    int k = 1;
    std::cout<<"thread a"<<std::endl;
    return;
}
void foo2(){
    int k = 1;
    std::cout<<"thread b"<<std::endl;
    return;
}
void foo3(){
    std::thread a(foo);
    std::thread b(foo2);
    a.detach();
    b.detach();
    return;
}
int main(){
    foo3();
    return 0;
}

Valgrind检测结果：

==63346== Memcheck, a memory error detector
==63346== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==63346== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==63346== Command: ./a.out
==63346== 
==63346== 
==63346== HEAP SUMMARY:
==63346==     in use at exit: 608 bytes in 4 blocks
==63346==   total heap usage: 5 allocs, 1 frees, 73,312 bytes allocated
==63346== 
==63346== 288 bytes in 1 blocks are possibly lost in loss record 3 of 4
==63346==    at 0x484DA83: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==63346==    by 0x40147D9: calloc (rtld-malloc.h:44)
==63346==    by 0x40147D9: allocate_dtv (dl-tls.c:375)
==63346==    by 0x40147D9: _dl_allocate_tls (dl-tls.c:634)
==63346==    by 0x4B4D834: allocate_stack (allocatestack.c:430)
==63346==    by 0x4B4D834: pthread_create@@GLIBC_2.34 (pthread_create.c:647)
==63346==    by 0x494A388: std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30)
==63346==    by 0x1095B9: std::thread::thread<void (&)(), , void>(void (&)()) (in /home/alan/Avionics/test/a.out)
==63346==    by 0x10935C: foo3() (in /home/alan/Avionics/test/a.out)
==63346==    by 0x109400: main (in /home/alan/Avionics/test/a.out)
==63346== 
==63346== 288 bytes in 1 blocks are possibly lost in loss record 4 of 4
==63346==    at 0x484DA83: calloc (in /usr/libexec/valgrind/vgpreload_memcheck-amd64-linux.so)
==63346==    by 0x40147D9: calloc (rtld-malloc.h:44)
==63346==    by 0x40147D9: allocate_dtv (dl-tls.c:375)
==63346==    by 0x40147D9: _dl_allocate_tls (dl-tls.c:634)
==63346==    by 0x4B4D834: allocate_stack (allocatestack.c:430)
==63346==    by 0x4B4D834: pthread_create@@GLIBC_2.34 (pthread_create.c:647)
==63346==    by 0x494A388: std::thread::_M_start_thread(std::unique_ptr<std::thread::_State, std::default_delete<std::thread::_State> >, void (*)()) (in /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.30)
==63346==    by 0x1095B9: std::thread::thread<void (&)(), , void>(void (&)()) (in /home/alan/Avionics/test/a.out)
==63346==    by 0x109372: foo3() (in /home/alan/Avionics/test/a.out)
==63346==    by 0x109400: main (in /home/alan/Avionics/test/a.out)
==63346== 
==63346== LEAK SUMMARY:
==63346==    definitely lost: 0 bytes in 0 blocks
==63346==    indirectly lost: 0 bytes in 0 blocks
==63346==      possibly lost: 576 bytes in 2 blocks
==63346==    still reachable: 32 bytes in 2 blocks
==63346==         suppressed: 0 bytes in 0 blocks
==63346== Reachable blocks (those to which a pointer was found) are not shown.
==63346== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==63346== 
==63346== For lists of detected and suppressed errors, rerun with: -s
==63346== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

原因解析 #

1. detach()的行为：调用detach()后，std::thread对象与底层的pthread资源完全分离，子线程成为"后台线程"，不再受主线程的std::thread对象管理。此时如果主线程（进程）先于子线程退出，进程会直接终止所有子线程，子线程的内部资源（比如TLS存储、线程栈相关的分配）来不及被pthread库的清理逻辑释放，Valgrind会将这些未被显式释放的内存标记为"possibly lost"。
2. join()的行为：join()会阻塞主线程，直到子线程执行完毕。子线程正常退出时，pthread库会自动回收其所有资源（包括TLS、线程栈等），因此Valgrind检测不到内存泄漏。

注意：这里的"possibly lost"并非真正的内存泄漏——操作系统会在进程终止时回收进程的所有内存资源。但从程序资源管理的规范性角度，这种情况应该避免。

解决方案与建议 #

• 优先使用join()：这是C++中管理线程生命周期最安全、最简洁的方式，能确保子线程资源被正确回收，避免Valgrind的误报（以及潜在的资源管理问题）。修改后的foo3()如下：

  void foo3(){
      std::thread a(foo);
      std::thread b(foo2);
      a.join();
      b.join();
      return;
  }
  

• 若必须使用detach()：需要确保子线程在主线程退出前完成执行。可以通过同步机制（比如std::condition_variable+std::mutex）让子线程通知主线程自己已结束，或者在主线程退出前添加足够的等待时间（不推荐，因为等待时间难以精确控制）。
• 区分Valgrind的泄漏类型："possibly lost"和"definitely lost"不同，前者是Valgrind无法确定内存是否还能被访问，后者是明确的泄漏。如果确认是detach导致的TLS资源问题，也可以通过Valgrind的抑制文件忽略这类误报，但这是最后的选择。

内容的提问来源于stack exchange，提问作者Alanyy