Fix pyauto flakiness by waiting for notification that the renderer process'

Fix pyauto flakiness by waiting for notification that the renderer process'
termination has been noticed by the browser before reloading the associated
tab.
BUG=64708
TEST=none

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

[kkania, 2010-12-10 18:16:50]

A short comment on why this is necessary:

I noticed in the database test, via logging, that the reload method in the
automation provider was being run before OnMsgRenderViewGone. The tab was
reloading and then receives news that the process crashed and goes to the sad
tab page.

We haven't noticed this problem before because the other test that killed the
renderer did it using the GetBrowser(0).GetTab(0).Reload(), which takes 3 round
trips to the browser instead of 1.

[AmolKher, 2010-12-10 18:56:43]

LGTM with comments.

http://codereview.chromium.org/5755003/diff/5001/chrome/browser/automation/au...
File chrome/browser/automation/automation_provider_observers.h (right):

http://codereview.chromium.org/5755003/diff/5001/chrome/browser/automation/au...
chrome/browser/automation/automation_provider_observers.h:996: // Allos the
automation provider to wait for a RENDERER_PROCESS_CLOSED
Allows

http://codereview.chromium.org/5755003/diff/5001/chrome/test/functional/brows...
File chrome/test/functional/browser.py (right):

http://codereview.chromium.org/5755003/diff/5001/chrome/test/functional/brows...
chrome/test/functional/browser.py:166: def testKillAndRelodRenderer(self):
:s/Relod/Reload

[Nirnimesh, 2010-12-10 20:45:29]

LGTM.
Thanks for investigating.