New issue
Advanced search Search tips

Issue 688534 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

BrowserDialogTest child process does not launch on Windows without waiting

Project Member Reported by bsep@chromium.org, Feb 3 2017

Issue description

When 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.
 
Can you clarify what the desired action for this bug is?  "Figure out why this happens and make callers not need to explicitly deal with it"?

Comment 2 by bsep@chromium.org, 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.
Project Member

Comment 3 by sheriffbot@chromium.org, Feb 12 2018

Status: Archived (was: Available)
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

Comment 4 by bsep@chromium.org, Feb 12 2018

Owner: bsep@chromium.org
Status: Assigned (was: Archived)
This is still an issue.

Sign in to add a comment