Status: Untriaged Owner: ---- Labels: Type-Bug Pri-3 OS-Linux Area-BrowserBackend Size-Medium Valgrind
New issue 19463 by [email protected]: Yet another memory leak in base::MessagePumpLibevent::MessagePumpLibevent()? http://code.google.com/p/chromium/issues/detail?id=19463 Probably same cause as bug 19385 and bug 19377, all three seem to have gotten rather frequent about the same time last week. This one is an event leak, probably nothing to worry about; it's easy to imagine an O(1) leak here. See for example http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Linux%20(valgrind)/builds/2329/steps/valgrind%20test:%20unit/logs/stdio Valgrind complains 1,980 (72 direct, 1,908 indirect) bytes in 1 blocks are definitely lost in loss record 21,540 of 21,804 operator new(unsigned int) (vg_replace_malloc.c:213) base::MessagePumpLibevent::Init() (base/message_pump_libevent.cc:124) 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 -~----------~----~----~----~------~----~------~--~---
