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

Issue 734518 link

Starred by 1 user

Issue metadata

Status: Archived
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression



Sign in to add a comment

ozone: initialization fails on exosphere drm clients

Reported by varadgau...@gmail.com, Jun 19 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0

Steps to reproduce the problem:
$ XDG_RUNTIME_DIR=/home/chronos chrome --user-data-dir=/home/chronos/ --ozone-platform=gbm --use-ozone-surfaceless --enable-wayland-server

$ XDG_RUNTIME_DIR=/home/chronos/ wayland_rects_client --use-drm
[0619/012550.312286:FATAL:thread_task_runner_handle.cc(28)] Check failed: current. 
#0 0x5638992562dd base::debug::StackTrace::StackTrace()
#1 0x563899254f2c base::debug::StackTrace::StackTrace()
#2 0x563899277f03 logging::LogMessage::~LogMessage()
#3 0x563899370f0c base::ThreadTaskRunnerHandle::Get()
#4 0x563899208367 ui::(anonymous namespace)::OzonePlatformGbm::InitializeGPU()
#5 0x563898fa3c35 ui::OzonePlatform::InitializeForGPU()
#6 0x563898ec58ea exo::wayland::clients::ClientBase::Init()
#7 0x563898eb6ece exo::wayland::clients::RectsClient::Run()
#8 0x563898eba167 main
#9 0x7943a864b816 __libc_start_main
#10 0x563898eb6d29 _start

Aborted (core dumped)

What is the expected behavior?
wayland_rects_client shouldn't abort.

What went wrong?
Commit 2fc984150a60b860103aa4d2f67d9c1686d340da does not check if base::ThreadTaskRunnerHandle is available before acquiring it (https://chromium.googlesource.com/chromium/src/+/2fc984150a60b860103aa4d2f67d9c1686d340da/ui/ozone/platform/drm/ozone_platform_gbm.cc#213), which causes the exosphere client process to crash when it tries to initialize ozone.

Did this work before? Yes pre-2fc984150a60b860103aa4d2f67d9c1686d340da

Chrome version: <Copy from: 'about:version'>  Channel: n/a
OS Version: 
Flash Version:
 
Components: OS>Kernel
Owner: sadrul@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by sadrul@chromium.org, Jul 13 2017

Cc: rjkroege@chromium.org sadrul@chromium.org reve...@chromium.org
Owner: dcasta...@chromium.org
Status: Fixed (was: Assigned)
Should be fixed by https://chromium-review.googlesource.com/c/551295/

Comment 3 by dchan@chromium.org, Jan 22 2018

Status: Archived (was: Fixed)

Sign in to add a comment