Comment #2 on issue 20320 by d...@chromium.org: Memory leak in BrowserWindowGtk::Close() http://code.google.com/p/chromium/issues/detail?id=20320
Variant seen once today in http://build.chromium.org/buildbot/waterfall/builders/Linux%20UI%201%20of%203%20(valgrind)/builds/80/steps/valgrind%20test:%20ui/logs/stdio This variant's stack is so long we can't see what triggered it in our code. 12 bytes in 1 blocks are definitely lost in loss record 1,782 of 10,802 malloc (vg_replace_malloc.c:194) g_malloc (glib2.0-2.16.6/glib/gmem.c:131) g_slice_alloc (glib2.0-2.16.6/glib/gslice.c:824) handlers_find (glib2.0-2.16.6/gobject/gsignal.c:392) signal_handlers_foreach_matched_R (glib2.0-2.16.6/gobject/gsignal.c:1849) g_signal_handlers_disconnect_matched (glib2.0-2.16.6/gobject/gsignal.c:1934) gtk_accel_label_set_accel_widget (gtk+2.0-2.12.9/gtk/gtkaccellabel.c:396) gtk_accel_label_destroy (gtk+2.0-2.12.9/gtk/gtkaccellabel.c:204) ... gtk_object_dispose (gtkobject.c:418) -- 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 -~----------~----~----~----~------~----~------~--~---
