Fix a browser, renderer, plugin deadlock caused by the change to reparent plugin windows in the b...

Fix a browser, renderer, plugin deadlock caused by the change to reparent plugin windows in the browser
process. Reparenting occurs via Windows API calls on the IO thread which can result in window messages
being dispatched to plugin windows which may be blocked on outgoing sync calls.

Fix is to execute the Windows API calls on the UI thread.

Fixes bug http://code.google.com/p/chromium/issues/detail?id=85397

BUG=85397
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=88393

[cpu_(ooo_6.6-7.5), 2011-06-08 18:04:31]

http://codereview.chromium.org/6995082/diff/1/content/browser/plugin_process_...
File content/browser/plugin_process_host.cc (right):

http://codereview.chromium.org/6995082/diff/1/content/browser/plugin_process_...
content/browser/plugin_process_host.cc:86: NewRunnableFunction(::SetParent,
window, parent));
Is not easier to just make a single function that does all the 3 things and call
it via PostTask?

[ananta, 2011-06-08 18:10:47]

http://codereview.chromium.org/6995082/diff/1/content/browser/plugin_process_...
File content/browser/plugin_process_host.cc (right):

http://codereview.chromium.org/6995082/diff/1/content/browser/plugin_process_...
content/browser/plugin_process_host.cc:86: NewRunnableFunction(::SetParent,
window, parent));
On 2011/06/08 18:04:31, cpu wrote:
> Is not easier to just make a single function that does all the 3 things and
call
> it via PostTask?

Done.

[cpu_(ooo_6.6-7.5), 2011-06-08 19:55:38]

lgtm