diff options
author | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-28 22:32:21 +0000 |
---|---|---|
committer | jam@chromium.org <jam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-09-28 22:32:21 +0000 |
commit | 12636df0dcf36c769c8a5940d6a0c0b6b6a6647c (patch) | |
tree | 5ff7eccca7457afe24c47a277286c834108e825c /chrome/common/render_messages_internal.h | |
parent | ca3f22c070a6b61a3ec40ace07244890bbdd6ebe (diff) | |
download | chromium_src-12636df0dcf36c769c8a5940d6a0c0b6b6a6647c.zip chromium_src-12636df0dcf36c769c8a5940d6a0c0b6b6a6647c.tar.gz chromium_src-12636df0dcf36c769c8a5940d6a0c0b6b6a6647c.tar.bz2 |
Fix deadlock when plugin puts an alert and right afterwards the browser process makes a win32 call that ends up waiting on the plugin. Since the plugin thread is blocked, the Windows message doesn't get dispatched and the browser ui thread deadlocks. The message from the renderer would make the plugin run a nested message loop but it doesn't get run on the browser ui thread since it's blocked. The fix is to set the event that runs nested message loop in the renderer process.
BUG=23147
TEST=ui tests already cover nested message loops and plugins. This particular scenario is hard to write a test case for because it's a race condition involving the browser.
Review URL: http://codereview.chromium.org/243018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@27421 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/render_messages_internal.h')
-rw-r--r-- | chrome/common/render_messages_internal.h | 11 |
1 files changed, 4 insertions, 7 deletions
diff --git a/chrome/common/render_messages_internal.h b/chrome/common/render_messages_internal.h index ac124b5..28dc35b 100644 --- a/chrome/common/render_messages_internal.h +++ b/chrome/common/render_messages_internal.h @@ -69,9 +69,8 @@ IPC_BEGIN_MESSAGES(View) // Tells the renderer to create a new view. // This message is slightly different, the view it takes is the view to // create, the message itself is sent as a non-view control message. - IPC_MESSAGE_CONTROL5(ViewMsg_New, + IPC_MESSAGE_CONTROL4(ViewMsg_New, gfx::NativeViewId, /* parent window */ - ModalDialogEvent, /* model dialog box event */ RendererPreferences, WebPreferences, int32 /* view id */) @@ -769,13 +768,11 @@ IPC_END_MESSAGES(View) IPC_BEGIN_MESSAGES(ViewHost) // Sent by the renderer when it is creating a new window. The browser creates // a tab for it and responds with a ViewMsg_CreatingNew_ACK. If route_id is - // MSG_ROUTING_NONE, the view couldn't be created. modal_dialog_event is set - // by the browser when a modal dialog is shown. - IPC_SYNC_MESSAGE_CONTROL2_2(ViewHostMsg_CreateWindow, + // MSG_ROUTING_NONE, the view couldn't be created. + IPC_SYNC_MESSAGE_CONTROL2_1(ViewHostMsg_CreateWindow, int /* opener_id */, bool /* user_gesture */, - int /* route_id */, - ModalDialogEvent /* modal_dialog_event */) + int /* route_id */) // Similar to ViewHostMsg_CreateWindow, except used for sub-widgets, like // <select> dropdowns. This message is sent to the TabContents that |