It's not safe to delete the balloon view during MenuDelegate::StoppedShowing,...

chrome/browser/ui/gtk/notifications/balloon_view_gtk.cc

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "chrome/browser/ui/gtk/notifications/balloon_view_gtk.h"
 
 #include <gtk/gtk.h>
 
 #include <string>
 #include <vector>
@@ skipping 441 matching lines @@
 }
 
 void BalloonViewImpl::OnOptionsMenuButton(GtkWidget* widget,
                                           GdkEventButton* event) {
   menu_showing_ = true;
   options_menu_->PopupForWidget(widget, event->button, event->time);
 }
 
 // Called when the menu stops showing.
 void BalloonViewImpl::StoppedShowing() {
-  if (pending_close_)
-    DelayedClose(false);
   menu_showing_ = false;
+  if (pending_close_) {
+    MessageLoop::current()->PostTask(
+        FROM_HERE,
+        method_factory_.NewRunnableMethod(
+            &BalloonViewImpl::DelayedClose, false));
+  }

[Andrew T Wilson (Slow), 2011/02/23 00:43:58]

So, is the intent that DelayedClose() should never be called directly, but only
via PostTask? If so, we should probably document this. I'm guessing the idea is
that it *could* be called directly, even though it isn't currently.

 }
 
 gboolean BalloonViewImpl::OnDestroy(GtkWidget* widget) {
   frame_container_ = NULL;
   Close(false);
   return FALSE;  // Propagate.
 }