summaryrefslogtreecommitdiff
path: root/dev-cpp/threadpool/files/threadpool-0.2.5-memleak.patch
diff options
context:
space:
mode:
Diffstat (limited to 'dev-cpp/threadpool/files/threadpool-0.2.5-memleak.patch')
-rw-r--r--dev-cpp/threadpool/files/threadpool-0.2.5-memleak.patch22
1 files changed, 0 insertions, 22 deletions
diff --git a/dev-cpp/threadpool/files/threadpool-0.2.5-memleak.patch b/dev-cpp/threadpool/files/threadpool-0.2.5-memleak.patch
deleted file mode 100644
index 26d89d1d5c25..000000000000
--- a/dev-cpp/threadpool/files/threadpool-0.2.5-memleak.patch
+++ /dev/null
@@ -1,22 +0,0 @@
-Fix memleak due circular references blocking garbage collection.
-
-http://www.cplusplus.com/forum/general/56971/ provides a testcase for a memory
-leak with the threadpool due to shared_ptr usage.
-
-I really needed threadpool to work for me, so I traced & fixed it as best as
-possible. When the threadpool is being destroyed, your threads should have
-terminated already. Do so deliberately if not done yet, so that they free the
-memory.
-
-Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
-
---- threadpool/boost/threadpool/detail/pool_core.hpp
-+++ threadpool/boost/threadpool/detail/pool_core.hpp
-@@ -150,6 +150,7 @@
- /// Destructor.
- ~pool_core()
- {
-+ terminate_all_workers(true);
- }
-
- /*! Gets the size controller which manages the number of threads in the pool.