Possible memory leak with DEBUG_LOCKORDER #1550

issue TheBlueMatt opened this issue on July 3, 2012
  1. TheBlueMatt commented at 1:38 AM on July 3, 2012: member

    About boost::thread_specific_ptr: "Note: on some platforms, cleanup of thread-specific data is not performed for threads created with the platform's native API. On those platforms such cleanup is only done for threads that are started with boost::thread unless boost::on_thread_exit() is called manually from that thread." Thus the lockstack object in sync.cpp may never be deleted. This is only really an issue due to recent RPC changes where long-running nodes may have seen many, many RPC threads.

  2. laanwj commented at 9:42 AM on May 18, 2015: member

    The number of RPC threads created by bitcoind is bounded at -rpcthreads=<n>. These are created during initialization and terminated at shutdown. The memory leak will be thus be bounded to that number too. I don't see this as a serious issue.

  3. laanwj closed this on May 18, 2015

  4. suprnurd referenced this in commit 4df8a20f96 on Dec 5, 2017
  5. lateminer referenced this in commit f246e104e5 on May 6, 2020
  6. MarcoFalke locked this on Sep 8, 2021
Contributors
Labels

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 21:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me