Comment #3 on issue 20320 by d...@chromium.org: Memory leak in BrowserWindowGtk::Close() http://code.google.com/p/chromium/issues/detail?id=20320
Another variant: http://build.chromium.org/buildbot/waterfall/builders/Linux%20UI%201%20of%203%20(valgrind)/builds/90/steps/valgrind%20test:%20ui/logs/stdio 7 bytes in 1 blocks are definitely lost in loss record 348 of 12,334 malloc (vg_replace_malloc.c:194) g_malloc (glib2.0-2.16.6/glib/gmem.c:131) gtk_accelerator_name (gtk+2.0-2.12.9/gtk/gtkaccelgroup.c:1175) gtk_accel_group_disconnect (gtk+2.0-2.12.9/gtk/gtkaccelgroup.c:411) gtk_accel_group_disconnect_key (gtk+2.0-2.12.9/gtk/gtkaccelgroup.c:625) BrowserWindowGtk::Close() (chrome/browser/gtk/browser_window_gtk.cc:790) -- 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 -~----------~----~----~----~------~----~------~--~---
