https://sourceforge.net/p/threadpool/bugs/6/Recent changes to 6: Error in pool destructionenWed, 20 Oct 2010 20:59:45 -0000https://sourceforge.net/p/threadpool/bugs/6/<div class="markdown_content"><p>Hello. I have the following set of events:</p> <p>1. I have a .dll that uses fifo_pool.</p> <p>2. Pool gets destructed.</p> <p>2.1. terminate_all_workers (wait_for_all_tasks shutdown policy) notify all workers to quit.</p> <p>2.2. All workers were already finished with their tasks, so, there's no wait</p> <p>2.3.1. Worker threads gets notification they should be quit, they clean up and, at the end, they add themselves to the m_terminated_workers collection</p> <p>2.3.2. Back in terminate_all_workers; m_terminated_workers collection is iterated and all threads there are joined. However, at this point, m_terminated_workers collection IS EMPTY. The sequence was notify all and then no wait, so, threads are ready to be run, but, they are possibly not scheduled yet.</p> <p>2.4. Pool destructor is done.</p> <p>3. My dll is unloaded.</p> <p>4. Worker threads eventually get scheduled and BOOM - process crashes because there's no more code to execute.</p> <p>Does this explanation makes any sense? Is there a fix for this? Tnx.</p></div>gmitWed, 20 Oct 2010 20:59:45 -0000https://sourceforge.net5a58ddb32730650e027ef0599b03817fc73c22b3