Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-2 OS-Mac Area-Misc Size-Medium valgrind

New issue 21279 by [email protected]: Memory leak in  
VisitedLinkMaster::TabbleBuilder::OnComplete
http://code.google.com/p/chromium/issues/detail?id=21279

http://chrome-
buildbot.corp.google.com:8016/builders/Mac%20UI%203%20of%203%20(va
lgrind)/builds/1208/steps/valgrind%20test:%20ui/logs/stdio

32 bytes in 1 blocks are definitely lost in loss record 3,448 of 6,777
   operator new(unsigned long) (sers/chrome-bot/valgrind-
10771/coregrind/m_replacemalloc/vg_replace_malloc.c:220)
   std::_Rb_tree<tracked_objects::Location,
std::pair<tracked_objects::Location const, tracked_objects::Births*>,
std::_Select1st<std::pair<tracked_objects::Location const,
tracked_objects::Births*> >, std::less<tracked_objects::Location>,
std::allocator<std::pair<tracked_objects::Location const,
tracked_objects::Births*> > >::_M_insert(std::_Rb_tree_node_base*,
std::_Rb_tree_node_base*, std::pair<tracked_objects::Location const,
tracked_objects::Births*> const&) (stl_tree.h:356)
   std::_Rb_tree<tracked_objects::Location,
std::pair<tracked_objects::Location const, tracked_objects::Births*>,
std::_Select1st<std::pair<tracked_objects::Location const,
tracked_objects::Births*> >, std::less<tracked_objects::Location>,
std::allocator<std::pair<tracked_objects::Location const,
tracked_objects::Births*> >
> ::insert_unique(std::_Rb_tree_iterator<std::pair<tracked_objects::Location
const, tracked_objects::Births*> >, std::pair<tracked_objects::Location
const, tracked_objects::Births*> const&) (stl_tree.h:903)
   tracked_objects::ThreadData::FindLifetime(tracked_objects::Location
const&) (stl_map.h:384)
   tracked_objects::Tracked::SetBirthPlace(tracked_objects::Location const&)
(/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/tracked.cc:80)
   MessageLoop::PostTask_Helper(tracked_objects::Location const&, Task*,
long long, bool) (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_loop.cc:254)
   MessageLoop::PostTask(tracked_objects::Location const&, Task*)
(/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_loop.cc:232)
   VisitedLinkMaster::TableBuilder::OnComplete(bool) (/b/slave/chromium-
rel-mac-valgrind-ui-
3/build/src/chrome/browser/visitedlink_master.cc:1028)
   history::HistoryBackend::IterateURLs(HistoryService::URLEnumerator*)
(/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/chrome/browser/history/history_backend.cc:829)
   RunnableMethod<history::HistoryBackend, void
(history::HistoryBackend::*)(HistoryService::URLEnumerator*),
Tuple1<HistoryService::URLEnumerator*> >::Run() (tuple.h:422)
   MessageLoop::RunTask(Task*) (/b/slave/chromium-rel-mac-valgrind-
ui-3/build/src/base/message_loop.cc:314)
   MessageLoop::DeferOrRunPendingTask(MessageLoop::PendingTask
const&) (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_loop.cc:322)
   MessageLoop::DoWork() (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_loop.cc:429)
   base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
(/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_pump_default.cc:23)
   MessageLoop::RunInternal() (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_loop.cc:199)
   MessageLoop::RunHandler() (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_loop.cc:181)
   MessageLoop::Run() (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/message_loop.cc:155)
   base::Thread::ThreadMain() (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/thread.cc:156)
   ThreadFunc(void*) (/b/slave/chromium-rel-mac-valgrind-ui-
3/build/src/base/platform_thread_posix.cc:26)
   _pthread_start
   thread_start

Not sure if this is related to bug 20659, or just happening to get memory
from the same place and then leaking it differently.

--
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to