New issue
Advanced search Search tips

Issue 746625 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Mash Browser Tests --single_process does not work

Project Member Reported by jonr...@chromium.org, Jul 19 2017

Issue description

Right now there is actually an infinite loop.
   -MashBrowserTestsMain::CreateServiceManagerConnection is registered as the content::ServiceManagerConnection factory.
   -BrowserMainLoop goes to init a ServiceManagerContext triggering the factory.
   -But the factory we registered ends up calling ServiceManagerConnection::Create. Which calls the factory.... thereby infinitely looping.

When this isn't occurring there is a crash in the GpuService as we are attempting to start all services in the same process.

We only want to start the test case, normally a child process, in the same process as the host.

All services should still be spun up in their own processes
 
Components: -Internals>MUS Internals>Services>WindowService
Cc: jamescook@chromium.org
Owner: ----
Status: Untriaged (was: Available)
Hey James,

This is another one I've seen in my backlog. With all the process structure changes in the last year I'm not sure if this is still a problem

Sign in to add a comment