Comment #3 on issue 3782 by [email protected]:
ObjectWatcher::StartWatching() failure in
SessionRestoreUITest.ClosedTabStaysClosed
http://code.google.com/p/chromium/issues/detail?id=3782
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=8651
------------------------------------------------------------------------
r8651 | [email protected] | 2009-01-26 11:38:05 -0800 (Mon, 26 Jan 2009) |
11 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/chrome/browser/renderer_host/browser_render_process_host.cc?r1=8651&r2=8650
Close the handle to the child process after terminating it. This avoids
calling RegisterWaitForSingleObject with a handle to a process that has
already been terminated. (See the use of ProcessWatcher in the destructor
of BrowserRenderProcessHost.) I'm not sure that this explains why RWFSO
fails, but it seems like a reasonable change anyways. The MSDN docs do
not give any reasons for why RWFSO might fail.
R=maruel
BUG=3782
Review URL: http://codereview.chromium.org/18810
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
