Status: Untriaged Owner: ---- Labels: Type-Bug Pri-2 OS-Linux Area-Misc Size-Medium Valgrind
New issue 19385 by d...@chromium.org: Another leak in base::MessagePumpLibevent::MessagePumpLibevent()? http://code.google.com/p/chromium/issues/detail?id=19385 Like bug 19377 http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Linux%20(valgrind)/builds/2282/steps/valgrind%20test:%20unit/logs/stdio 1,980 (512 direct, 1,468 indirect) bytes in 1 blocks are definitely lost in loss record 21,498 of 21,755 realloc (vg_replace_malloc.c:473) epoll_add (third_party/libevent/epoll.c:167) event_add (third_party/libevent/event.c:723) base::MessagePumpLibevent::Init() (base/message_pump_libevent.cc:129) base::MessagePumpLibevent::MessagePumpLibevent() (base/message_pump_libevent.cc:103) MessageLoop::MessageLoop(MessageLoop::Type) (base/message_loop.cc:106) base::Thread::ThreadMain() (base/thread.cc:140) ThreadFunc(void*) (base/platform_thread_posix.cc:26) start_thread (/lib/tls/i686/cmov/libpthread-2.7.so) -- 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 -~----------~----~----~----~------~----~------~--~---
