Boost C++ Libraries: Ticket #5754: Bug/design issue with boost::thread::id

owner, status changed; keywords set

viboes — Sun, 11 Dec 2011 09:53:49 GMT

keywords thread::id added
owner changed from Anthony Williams to viboes
status new → assigned

I was wondering what prevent from making thread::id an opaque type around the thread::native_handle, Anthony? Shouldn't the native handle solve this issue?

type changed; cc set

viboes — Sun, 11 Dec 2011 09:57:04 GMT

cc viboes added
type Bugs → Support Requests

Can this be considered a duplicate of #4345 thread::id and joining problem with cascade of threads?

Moved to support request until clarified.

status, type changed; resolution set

viboes — Sat, 31 Dec 2011 15:09:54 GMT

status assigned → closed
type Support Requests → Bugs
resolution → duplicate

duplicate of #4345 thread::id and joining problem with cascade of threads

anonymous — Thu, 08 Mar 2012 16:16:02 GMT

Replying to viboes:

duplicate of #4345 thread::id and joining problem with cascade of threads

I have encountered another manifestation of this issue. I have produced a very simple test program that will exhibit the issue:

#include <boost/thread.hpp>
#include <boost/shared_ptr.hpp>
void GetThreadId(boost::shared_ptr<boost::thread::id> tidPtr)
{
    *tidPtr = boost::this_thread::get_id();
}
int main(int argc, char* argv[])
{
    for(;;)
    {
        boost::shared_ptr<boost::thread::id> tidPtr(new boost::thread::id());
        boost::thread thread(GetThreadId, tidPtr);
        tidPtr.reset(); // force necessity to pass tidPtr by value
        thread.join();
    }
    return 0;
}

This program leaks memory every time around the for loop in main.