New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 1 user

Issue metadata

Status: Archived
Closed: Jan 2017
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Sign in to add a comment

mustash is broken running with Ozone DRM

Project Member Reported by, Jan 10 2017 Back to list

Issue description

Trying to run mustash on a Chromebook device with Ozone DRM is broken currently. There is a crash on ui::Service::OnStart() when it launches and everything fails with the WS.

The crash in particular happens when XkbKeyboardLayoutEngine::SetCurrentLayoutByName() is called, or if that is moved then when other Ozone DRM functionality gets called later. The root cause is that there is no base::TaskScheduler instance. It looks many things got switch from using WorkerPool to TaskRunner last week.

Calling base::TaskScheduler::CreateAndSetSimpleTaskScheduler() near the start of Service::OnStart() fixes the crash. I'm not sure if we need to specify any TaskScheduler params or how many worker threads we want.

Status: Started
Project Member

Comment 2 by, Jan 11 2017

The following revision refers to this bug:

commit 3ae6c6b59c0c9a5609fb220d7c494649ad1e826a
Author: kylechar <>
Date: Wed Jan 11 18:13:30 2017

Create TaskScheduler for all Mojo apps.

Running mustash on device currently crashes on startup. This is because
ui::Service doesn't create a TaskScheduler before Ozone DRM uses it. One
option is to have ui::Service::OnStart() create a TaskScheduler. If
other Mojo applications need a task scheduler they'll have to do the
same. Instead, have MashRunner start a TaskRunner for each process.

This fixes the crash in Ozone DRM and doesn't seem to cause any other

BUG= 679840 

Cr-Commit-Position: refs/heads/master@{#442956}


Status: Fixed

Comment 4 by, Mar 4 2017

Labels: VerifyIn-58

Comment 5 by, Apr 17 2017

Labels: VerifyIn-59

Comment 6 by, May 30 2017

Labels: VerifyIn-60

Comment 7 by, Aug 1 2017

Labels: VerifyIn-61
Status: Archived

Sign in to add a comment