Comment #5 on issue 16093 by [email protected]: Memory leaks in net::HostResolver http://code.google.com/p/chromium/issues/detail?id=16093
I can't repro this. I tried your provided command: sh tools/valgrind/chrome_tests.sh -t ui --gtest_filter=OmniboxTest.Measure. I also tried valgrind --leak-check=full sconsbuild/Debug/ui_tests -- gtest_filter=RedirectTest.*. Neither shows either of the stacktraces you listed (are they the full stacktraces?). I also don't believe these are true leaks. The host resolver runs on the WorkerPool threads, which in Linux are not provided by a system thread pool, so we just start up pthreads which we never join. Therefore, I suspect valgrind thinks that these are leaks even though the Task in the WorkerPool still has pointers to all the data. -- 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 -~----------~----~----~----~------~----~------~--~---
