Comment #6 on issue 16096 by [email protected]: Thread name leak in PlatformThread::SetName http://code.google.com/p/chromium/issues/detail?id=16096
Dan, I'm not convinced this is a leak. Take a look at the std::string, it's being stack allocated in WorkerThread::ThreadMain, which is alive at the end of the program. It's not being freed because the stack variable that has the pointer to the heap allocated buffer for the string is still alive in the thread stack. I cannot repro this valgrind error on my system, nor can Elliot on his. We are using gHardy. The same comment goes for bug 16093. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
