exe:chrome won't start on device |
||||||
Issue descriptionTrying to launch exe:chrome on a Pixel results in chrome crashing. It produces the following stack trace. [16956:16956:0415/132814:FATAL:cros_dbus_service.cc(83)] Failed to own: org.chromium.LibCrosService #0 0x7fab57264894 base::debug::StackTrace::StackTrace() #1 0x7fab572827ce logging::LogMessage::~LogMessage() #2 0x7fab519d34d0 chromeos::CrosDBusServiceImpl::OnOwnership() #3 0x7fab50c13c19 _ZN4base8internal7InvokerINS_13IndexSequenceIJLm0ELm1EEEENS0_9BindStateINS_8CallbackIFvRKNS_8FilePathEbELNS0_8CopyModeE1EEES9_JS8_RbEEENS0_12InvokeHelperILb0EvSB_EEFvvEE3RunEPNS0_13BindStateBaseE #4 0x7fab572662ca base::debug::TaskAnnotator::RunTask() #5 0x7fab5728c5a2 base::MessageLoop::RunTask() #6 0x7fab5728c9fe base::MessageLoop::DeferOrRunPendingTask() #7 0x7fab5728e144 base::MessageLoop::DoWork() #8 0x7fab57290929 base::MessagePumpLibevent::Run() #9 0x7fab5728d499 base::MessageLoop::RunHandler() #10 0x7fab572b8b08 base::RunLoop::Run() #11 0x7fab52c7260e content::MojoShellConnectionImpl::WaitForShellIfNecessary() #12 0x7fab52c72dc9 content::MojoShellConnectionImpl::BindToRequestFromCommandLine() #13 0x7fab526b438f content::BrowserMainLoop::PreMainMessageLoopRun() #14 0x7fab52aac50f content::StartupTaskRunner::RunAllTasksNow() #15 0x7fab526b775d content::BrowserMainLoop::CreateStartupTasks() #16 0x7fab526bb7c0 content::BrowserMainRunnerImpl::Initialize() #17 0x7fab526b3af2 content::BrowserMain() #18 0x7fab571b0a30 content::RunNamedProcessTypeMain() #19 0x7fab571b0b5c content::ContentMainRunnerImpl::Run() #20 0x7fab571aedb9 content::ContentMain() #21 0x7fab5077a282 ChromeMain #22 0x7fab4e2e6fb6 __libc_start_main #23 0x7fab5077a0af <unknown>
,
Apr 15 2016
Running mash_session on device with the following arguments: ./chrome --mash --ash-host-window-bounds=2560x1700 The chrome browser crashes on startup with the above stack trace. If I run "exe:chrome" via QuickLaunch it crashes again with the same stack trace.
,
Apr 15 2016
Hm, did you do 'stop ui' before running that? The error message looks familiar to me, and I seem to remember 'stop ui' fixing it.
,
Apr 15 2016
Yes, stop ui is done before this. The mash_session GUI starts properly and other mojo apps can be run from QuickLaunch. It's just the chrome browser that doesn't work on device. The chrome browser works fine with the same commands under Oxygen, likely because it doesn't need to use dbus off device?
,
Apr 19 2016
,
Apr 19 2016
,
Apr 20 2016
The dbus problem occurs because of security issues with running chrome process as root. On Chrome OS it looks like it's supposed to run as chronos. Here is a sample command line to start as the correct user and specify some necessary flags when not running as root. sudo -u chronos ./chrome --mash --ash-host-window-bounds=2560x1700 --user-data-dir=/home/chronos --homedir=/ With that problem fixed it crashes accessing OzonePlatform in a new place.
,
Apr 20 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ff1c72875659748df13118ee4446a303b0c9c3a2 commit ff1c72875659748df13118ee4446a303b0c9c3a2 Author: kylechar <kylechar@chromium.org> Date: Wed Apr 20 19:24:13 2016 Use FakeImeKeyboard when running in mash. The OzonePlatform instance doesn't exist in the chrome browser process when running mash. ImeKeyboardOzone tries to access the instance and crashes. Always use FakeImeKeyboard with mash until mash IME work is started and this can be done properly. BUG= 603959 Review URL: https://codereview.chromium.org/1908583002 Cr-Commit-Position: refs/heads/master@{#388547} [modify] https://crrev.com/ff1c72875659748df13118ee4446a303b0c9c3a2/chrome/browser/chromeos/input_method/input_method_manager_impl.cc
,
Apr 20 2016
Chrome browser should now be able to start on device (with the WIP patch from rjkroege@). It still crashes quickly due to crbug.com/604109 and crbug.com/605218 but it will start.
,
Feb 26 2018
,
Feb 26 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sadrul@chromium.org
, Apr 15 2016