Comment #11 on issue 10737 by [email protected]: Memory leak in BrowserWindowGtk::ConnectAccelerators http://code.google.com/p/chromium/issues/detail?id=10737
Heh. Now it's showing up in the reference build. Should we update our reference build? 1,036 (740 direct, 296 indirect) bytes in 37 blocks are definitely lost in loss record 459 of 576 calloc (ome/chrome-bot/valgrind-10413-forkfix/coregrind/m_replacemalloc/vg_replace_malloc.c:415) g_malloc0 (ild/buildd/glib2.0-2.16.6/glib/gmem.c:151) g_closure_new_simple (ild/buildd/glib2.0-2.16.6/gobject/gclosure.c:97) g_cclosure_new (ild/buildd/glib2.0-2.16.6/gobject/gclosure.c:525) BrowserWindowGtk::ConnectAccelerators() (/b/slave/chromium-dbg-linux-valgrind- BrowserWindowGtk::BrowserWindowGtk(Browser*) (/b/slave/chromium-dbg-linux-valgrind- BrowserWindow::CreateBrowserWindow(Browser*) (/b/slave/chromium-dbg-linux-valgrind- -- 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 -~----------~----~----~----~------~----~------~--~---
