Status: Assigned Owner: [email protected] CC: [email protected], [email protected], [email protected] Labels: Type-Bug Pri-1 OS-Mac Area-DevTools Dogfood Valgrind Mstone-2.1
New issue 9565 by [email protected]: Mem leak in test_shell_tests - MimeTypeTests.MimeTypeTests http://code.google.com/p/chromium/issues/detail?id=9565 Valgrind on Mac thinks that test_shell_tests leaks memory. We want to enable auto-analysis on valgrind output, before which the detected leaks need to be fixed (or suppressed). I'm marking it to you since you were the last person to have touched this. If this is an error, please feel free to reassign to someone more appropriate (or bounce back to me). The leaking test is: MimeTypeTests.MimeTypeTests (mimetype_unittest.cc) The following is valgrind's output. (Refer waterfall for latest). ==23659== 181 bytes in 1 blocks are definitely lost in loss record 565 of 680 ==23659== at 0x4509E23: malloc_zone_malloc (vg_replace_malloc.c:197) ==23659== by 0x5CB184C: __setenv (in /usr/lib/libSystem.B.dylib) ==23659== by 0x5CB1175: setenv$UNIX2003 (in /usr/lib/libSystem.B.dylib) ==23659== by 0x36DCED: net::(anonymous namespace)::AppendToPythonPath(FilePath) (ssl_test_util.cc:172) ==23659== by 0x36DEFE: net::TestServerLauncher::SetPythonPath() (ssl_test_util.cc:175) ==23659== by 0x36E5B4: net::TestServerLauncher::Start(net::TestServerLauncher::Protocol, std::string const&, int, FilePath const&, FilePath const&) (ssl_test_util.cc:220) ==23659== by 0x401B2: BaseTestServer::Start(net::TestServerLauncher::Protocol, std::string const&, int, FilePath const&, FilePath const&, std::string const&, std::string const&) (url_request_context.h:76) ==23659== by 0x4089B: BaseTestServer::Start(net::TestServerLauncher::Protocol, std::string const&, int, FilePath const&, FilePath const&) (url_request_unittest.h:281) ==23659== by 0x40A10: UnittestTestServer::CreateServer() (url_request_unittest.h:284) ==23659== by 0x3D584: (anonymous namespace)::MimeTypeTests_MimeTypeTests_Test::TestBody() (mimetype_unittest.cc:23) ==23659== by 0x12A429: testing::Test::Run() (gtest.cc:2018) ==23659== by 0x12EF18: testing::internal::TestInfoImpl::Run() (gtest.cc:2250) ==23659== by 0x134FD4: testing::Message& testing::Message::operator<< <unsigned long long>(unsigned long long const&) (gtest-message.h:116) ==23659== by 0x12F8CE: testing::internal::List<testing::TestPartResult>::size() const (gtest- internal-inl.h:283) ==23659== by 0x12EE01: testing::UnitTest::Run() (gtest.cc:3403) ==23659== by 0x134FB8: testing::TestCase::RunTestCase(testing::TestCase*) (gtest- internal.h:97) ==23659== by 0x12F714: __gnu_cxx::__normal_iterator<testing::internal::ParameterizedTestCaseInfoBase**, std::vector<testing::internal::ParameterizedTestCaseInfoBase*, std::allocator<testing::internal::ParameterizedTestCaseInfoBase*> > >::operator++() (stl_iterator.h:623) ==23659== by 0x12EC6E: testing::internal::UnitTestImpl::RunAllTests() (gtest.cc:3655) ==23659== by 0x12ED63: testing::UnitTest::Run() (gtest.cc:3678) ==23659== by 0x7DDA6: CommandLine::ForCurrentProcess() (command_line.h:64) ==23659== by 0x29A5: (below main) (in src/xcodebuild/Debug/test_shell_tests) ==23659== -- 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 -~----------~----~----~----~------~----~------~--~---
