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

Issue 803593 link

Starred by 1 user
Status: WontFix
Owner:
msw@chromium.org
Closed: Jan 2018
Cc:
rjkroege@chromium.org
sadrul@chromium.org
kylec...@chromium.org
sky@chromium.org
osh...@chromium.org
mustash-bugs@google.com
mcasas@chromium.org
█ marc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug

Blocking:
issue 731255



Sign in to add a comment

mus: Crash trying to enter unified mode on device.

Project Member Reported by msw@chromium.org, Jan 18 2018 
mus: Crash trying to enter unified mode on device.

(1) Run 65.0.3319.0 on ToT @ #530231 on cyan per go/simplechrome
(2) Add --mus and --ash-dev-shortcuts flags to /etc/chrome_dev.conf per go/mustash-intro
(3) Enable "Unified desktop mode" in about:flags, connect a display.
(4) Press ctrl-shift-j to toggle into unified mode
Expected: Displays enter unified mode correctly.
Actual: Displays flicker off, return to login screen or device restarts; crash?

I'm not seeing anything pertinent in about:crashes or these logs from go/mustash-intro:
 /var/log/ui/ui.LATEST - stderr log (doesn’t have VLOGs, warnings)
 /home/chronos/user/log/chrome - post-login log
 /var/log/chrome/chrome - pre-login log

Does anyone know how to enable unified without the dev shortcut?
Can anyone help me track down these crashes? (I'm not very familiar with on-device logs/debugging)

This does not seem to repro on linux-desktop runs with:
  chrome --mus --screen-config=400x400,400x400 --ash-dev-shortcuts

Comment 1 by msw@chromium.org, Jan 18 2018

Status: Started (was: Assigned)
Talking with Oshima, I learned two valuable tidbits:
(1) about:settings/display should show an option to toggle unified (it doesn't in --mus)
(2) unified should be the default mode with the "Unified desktop mode" flag (mus winds up extended, maybe via crashing?)

I'll try to figure out why these things are happening, but might still need some on-device help.

Comment 2 by msw@chromium.org, Jan 18 2018 

Hmm, mus does have the unified option in about:settings/display with the commandline flag:
  chrome --mus --screen-config=400x400,400x400 --ash-enable-unified-desktop
I'm not sure what's happening on device...

Comment 3 by kylec...@chromium.org, Jan 18 2018 

Is mus still trying to create a PlatformWindow/AcceleratedWidget for the unified display?

Comment 4 by msw@chromium.org, Jan 18 2018 

I don't think so, I changed that in a very recent CL to use StubWindow (with |use_default_accelerated_widget == true|) to back the unified display, like cash:
  https://chromium-review.googlesource.com/c/chromium/src/+/862603

Comment 5 by msw@chromium.org, Jan 20 2018 

I don't get crashes on link... I'll need to test cyan again next week to confirm.
I do have issues with cursor/mouse warping, and event targeting...
I'll look deeper next week.

Comment 6 by sky@chromium.org, Jan 22 2018

Blocking: 731255

Comment 7 by msw@chromium.org, Jan 22 2018

Status: WontFix (was: Started)
I don't see crashes after updating my cyan device to 10328.0.0 / 66.0.3329.0 (ToT @ #530902)
I filed  Issue 804460  for the mouse/cursor/touch issues I'm seeing.

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

Components: -Internals>MUS Internals>Services>WindowService

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

Components: -MUS
►

Sign in to add a comment