Profiles: Fixed crash when avatar bubble is launched using ctrl+shift+m with only default profile

chrome/browser/ui/gtk/avatar_menu_button_gtk.cc

Index: chrome/browser/ui/gtk/avatar_menu_button_gtk.cc
diff --git a/chrome/browser/ui/gtk/avatar_menu_button_gtk.cc b/chrome/browser/ui/gtk/avatar_menu_button_gtk.cc
index c96a2ced64cc083e02f219c254003b7f8827fb1f..7de210c3c8c47b51023f512105fd22de753ea2f3 100644
--- a/chrome/browser/ui/gtk/avatar_menu_button_gtk.cc
+++ b/chrome/browser/ui/gtk/avatar_menu_button_gtk.cc
@@ -49,5 +49,6 @@ gboolean AvatarMenuButtonGtk::OnButtonPressed(GtkWidget* widget,
 }
 
 void AvatarMenuButtonGtk::ShowAvatarBubble() {
-  new AvatarMenuBubbleGtk(browser_, widget_.get(), arrow_location_, NULL);
+  if (gtk_widget_get_parent_window(widget_.get()))

[James Hawkins, 2011/12/01 17:15:55]

This isn't the same logic as ShouldDisplayAvatar().

[sail, 2011/12/01 19:12:23]

I think this is ok. ShoudDisplayAvatar decides if the button gets placed in the
title bar.

At this point we just want to know if we're in the title bar or not. If we're
not then we shouldn't show the bubble view.

I think a comment should be added to this code. Maybe something like:
// Only show the avatar bubble if the avatar button is in the title bar.

+    new AvatarMenuBubbleGtk(browser_, widget_.get(), arrow_location_, NULL);
 }