Comment #10 on issue 16096 by [email protected]: Thread name leak in PlatformThread::SetName http://code.google.com/p/chromium/issues/detail?id=16096
Actually, it just turns out that I'm an idiot and can't follow your repro directions. Using chrome_test.sh does repro for me. When I run valgrind directly, it doesn't show up as a leak. I'm looking at the valgrind test harness we have to see what setting is causing this difference. Currently this line doesn't repro: NSS_DISABLE_ARENA_FREE_LIST=1 G_SLICE=always-malloc valgrind --tool=memcheck --smc- check=all --num-callers=30 --demangle=no --trace-children=yes --leak-check=full -- suppressions=/usr/local/google/chromium2/src/tools/valgrind/memcheck/suppressions.txt /usr/local/google/chromium2/src/sconsbuild/Debug/ui_tests --ui-test-timeout=120000 -- ui-test-action-timeout=80000 --ui-test-action-max-timeout=180000 --ui-test-terminate- timeout=60000 --gtest_filter=OmniboxTest.Measure:- BrowserTest.ThirtyFourTabs:SessionRestoreUITest.* --gtest_print_time, timeout 120000 sec -- 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 -~----------~----~----~----~------~----~------~--~---
