Status: Untriaged Owner: ---- Labels: Type-Bug Pri-2 OS-Linux Area-BrowserBackend Size-Medium Valgrind
New issue 16104 by [email protected]: Memory leak in history::VisitSegmentDatabase::QuerySegmentUsage http://code.google.com/p/chromium/issues/detail?id=16104 Affects ui tests TabRestoreUITest.BasicRestoreFromClosedWindow, TabRestoreUITest.RestoreIntoSameWindow. Reproduce with e.g. sh tools/valgrind/chrome_test.sh -t ui -- Valgrind complains: 504 (224 direct, 280 indirect) bytes in 2 blocks are definitely lost in loss record 402 of 546 at operator new(unsigned int) (vg_replace_malloc.c:212) by history::VisitSegmentDatabase::QuerySegmentUsage(base::Time const&, int, std::vector<PageUsageData*, std::allocator<PageUsageData*> >*) (visitsegment_database.cc:270) by history::HistoryBackend::QueryTopURLsAndRedirects(...) (history_backend.cc:1174) by RunnableMethod<history::HistoryBackend, ... by MessageLoop::RunTask(Task*) (message_loop.cc:313) by MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask const&) (message_loop.cc:321) -- 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 -~----------~----~----~----~------~----~------~--~---
