HANG ui_tests harness though chrome.exe seemed to exit nicely

_From [bruen...@google.com](https://code.google.com/u/109494838902877177630/) on November 16, 2011 11:00:26_

I've seen this a number of times when I run chrome.exe under drmem via
BROWSER_WRAPPER but it's non-deterministic: the chrome window comes up,
the test completes, chrome.exe shuts down, but the harness never comes back
and sits there waiting. both chrome.exe instances are gone. from the logs
it's normal: the first exited cleanly (well, hit the drmem exit point:
maybe some unusual app exit), the 2nd didn't (which seems to happen even w/
-single-process but perhaps this is a 2nd tab that then is killed? =>
TOFILE)

ui_tests.exe itself is native. the question is, is chrome.exe exiting in a
non-standard way such that ui_tests doesn't detect it, and drmem is causing
that behavior? or is this some weird flakiness that gets tickled more
often w/ drmem? certainly some of the ui_tests seem to always hang until
the timeout, even natively, though AutomatedUITestBase.Home is not one of
those.

% BROWSER_WRAPPER='C:\src\drmemory\git\build_drmemory\bin\drmemory.exe -suppress C:\src\chromium\src\tools\valgrind\DrMemory\suppressions.txt -batch -pause_at_assert -quiet -no_results_to_stderr -no_check_uninitialized -no_count_leaks -dr c:/src/dr/git/exports --' ./ui_tests --single-process --ui-test-action-timeout=1200000 --ui-test-action-max-timeout=2800000 --ui-test-terminate-timeout=1200000 --gtest_filter="AutomatedUITestBase.Home"
Note: Google Test filter = AutomatedUITestBase.Home
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from AutomatedUITestBase
[ RUN ] AutomatedUITestBase.Home

_Original issue: http://code.google.com/p/drmemory/issues/detail?id=688_