BrowserDialogTest child process does not launch on Windows without waiting |
|||
Issue descriptionWhen using BrowserDialogTest on Windows the child process that actually launches the dialog never spawns. Example invocation: browser_tests.exe --gtest_filter=BrowserDialogTest.Invoke --dialog=CollectedCookiesTestMd, InvokeDialog_default --interactive Passing --single-process in is one workaround. Alternative workaround is to pass "options.wait = true" to base::LaunchProcess.
,
Feb 7 2017
Yes, "figure why this happens" is a good first step. I think the workaround is worrying mostly because we don't know what's going on, it might end up being normal and necessary.
,
Feb 12 2018
This issue has been available for more than 365 days with no owner or cc list, so archiving this bug. Please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 12 2018
This is still an issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by pkasting@chromium.org
, Feb 6 2017