New issue
Advanced search Search tips

Issue 796306 link

Starred by 1 user
Status: WontFix
Owner:
sky@chromium.org
Closed: Aug 14
Cc:
mustash-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

ash_standalone won't start, bad manifest, crashes

Project Member Reported by jamescook@chromium.org, Dec 19 2017 
ToT linux-chromeos r524487

out/Debug/mash --service=mash_session --window-manager=ash_standalone --ash-host-window-bounds="1024x768"

This hangs on startup:

[27029:27029:1219/124048.519461:4031805676:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: ash_standalone from binding interface: filesystem::mojom::Directory exposed by: catalog

If I fix the manifest with https://chromium-review.googlesource.com/#/c/chromium/src/+/834799 then it crashes in ash::Shell::Init() due to a null shell_delegate_->GetShellConnector() trying to do display init.

If I skip display init by passing display info on the command line:

out/Debug/mash --service=mash_session --window-manager=ash_standalone --ash-host-window-bounds="1024x768"

It crashes:

[25249:25260:1219/124000.146342:3983432794:INFO:service_process_launcher.cc(198)] Launched child process pid=25261, instance=, name=mash_session, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[25249:25260:1219/124000.299893:3983586127:INFO:service_process_launcher.cc(198)] Launched child process pid=25272, instance=, name=ash_standalone, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[25249:25260:1219/124000.846547:3984132786:INFO:service_process_launcher.cc(198)] Launched child process pid=25290, instance=, name=font_service, user_id=505C0EE9-3013-43C0-82B0-A84F50CF8D84
[25249:25260:1219/124000.948710:3984234948:INFO:service_process_launcher.cc(198)] Launched child process pid=25298, instance=, name=ui, user_id=b846a9cf-1cb0-42fa-9912-f7cfd33df70a
[25272:25272:1219/124001.140758:3984426975:ERROR:shell.cc(829)] JAMES context_factory (nil)
[25272:25272:1219/124001.140832:3984427043:ERROR:shell.cc(830)] JAMES context_factory_private (nil)
[25272:25272:1219/124001.140882:3984427092:ERROR:shell.cc(831)] JAMES connector 0x122c43d5fb80
[25249:25249:1219/124001.141986:3984428196:ERROR:instance.cc(49)] Unable to locate service manifest for local_state
[25249:25249:1219/124001.142031:3984428236:ERROR:service_manager.cc(890)] Failed to resolve service name: local_state
[25272:25272:1219/124001.144588:3984430802:FATAL:window_tree_host.cc(286)] Check failed: context_factory. 
#0 0x7f9240fd221d base::debug::StackTrace::StackTrace()
#1 0x7f9240fd079c base::debug::StackTrace::StackTrace()
#2 0x7f9241054a2d logging::LogMessage::~LogMessage()
#3 0x7f923ca0c883 aura::WindowTreeHost::CreateCompositor()
#4 0x7f923c9e3791 aura::WindowTreeHostMus::WindowTreeHostMus()
#5 0x7f9241da4a1d ash::AshWindowTreeHostMus::AshWindowTreeHostMus()
#6 0x7f9241f13800 ash::ShellPortMus::CreateAshWindowTreeHost()
#7 0x7f9241da35a3 ash::AshWindowTreeHost::Create()
#8 0x7f9241d62ae0 ash::WindowTreeHostManager::AddWindowTreeHostForDisplay()
#9 0x7f9241d62957 ash::WindowTreeHostManager::CreatePrimaryHost()
#10 0x7f9241eec812 ash::Shell::Init()
#11 0x7f9241ee6f97 ash::Shell::CreateInstance()
#12 0x7f92420a8e40 ash::WindowManager::CreateShell()
#13 0x7f92420a9341 ash::WindowManager::OnWmConnected()
#14 0x7f923c9be5a7 aura::WindowTreeClient::OnConnect()
#15 0x7f923ca60640 ui::mojom::WindowManagerStubDispatch::Accept()
#16 0x7f923c9e01b3 ui::mojom::WindowManagerStub<>::Accept()
#17 0x7f9242dbbc0f mojo::InterfaceEndpointClient::HandleValidatedMessage()
#18 0x7f9242dba781 mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept()
#19 0x7f9242db8e16 mojo::FilterChain::Accept()
#20 0x7f9242dbe4f6 mojo::InterfaceEndpointClient::HandleIncomingMessage()

Do we still need ash standalone? Removing it would simplify ui::Service() construction, since I think it's the last place we run the ui service in its own process.

To sky to decide if we want to fix this.

Comment 1 by jamescook@chromium.org, Dec 19 2017

Description: Show this description

Comment 2 by lafo...@chromium.org, Feb 26 2018

Components: -Internals>MUS Internals>Services>WindowService

Comment 3 by jamescook@chromium.org, Apr 19 2018

Components: -Internals>Services>WindowService Internals>Services>Ash
Labels: -Proj-Mustash-Mash

Comment 4 by jamescook@chromium.org, Apr 24 2018

Labels: -Proj-Mustash-Mus Proj-Mustash
Migrating Proj-Mustash-Mus to components Internals>Services>WindowService and Internals>Services>Ash

Comment 5 by jamescook@chromium.org, Aug 14

Status: WontFix (was: Assigned)
ash_standalone seems to be gone.
►

Sign in to add a comment