MOV link

https://drive.google.com/file/d/1LIPVUTFOhopnFtwaNSZ65sN4xOU-4ekC/view?usp=sharing

coreDumps

https://drive.google.com/file/d/1qpJ3T3xpRN0SuPNbOfvou6J-UTbQDrFe/view?usp=sharing

Added a number of CC's since this is blocking M64 stable for CrOS.  

This forked from crbug/809256.

From https://bugs.chromium.org/p/chromium/issues/detail?id=809256#c75
Comment by  xiyuan@chromium.org:


The mojo error is probably caused by chrome crash.

The crash in #74 is ARC kiosk related, in ArcRobotAuthCodeFetcher::Fetch:

  fetch_request_job_->SetDMToken(client->dm_token());

Suspect client->dm_token() somehow returns a bad string ref.

From core.chrome.1015:
====
Program terminated with signal SIGSEGV, Segmentation fault.
#0  std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__is_long (this=0x34) at /usr/bin/../include/c++/v1/string:1226
1226            {return bool(__r_.first().__s.__size_ & __short_mask);}
[Current thread is 1 (LWP 1015)]
(gdb) bt
#0  std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__is_long (this=0x34) at /usr/bin/../include/c++/v1/string:1226
#1  std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__get_pointer (this=<optimized out>) at /usr/bin/../include/c++/v1/string:1320
#2  std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::data (this=<optimized out>) at /usr/bin/../include/c++/v1/string:1134
#3  std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::operator= (this=0xe6b1020, __str=...) at /usr/bin/../include/c++/v1/string:2047
#4  policy::DeviceManagementRequestJob::SetDMToken (this=0xe6b1000, dm_token=...)
    at ../../../../../../../home/chrome-bot/chrome_root/src/components/policy/core/common/cloud/device_management_service.cc:479
#5  0x05e97396 in arc::ArcRobotAuthCodeFetcher::Fetch(base::RepeatingCallback<void (bool, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&)> const&) (this=0xfd05450, callback=...) at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/arc/auth/arc_robot_auth_code_fetcher.cc:54
#6  0x05e95a64 in arc::ArcAuthService::RequestAccountInfo (this=0xfc653e0, initial_signin=<optimized out>)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/arc/auth/arc_auth_service.cc:247
#7  0x05e153ba in arc::mojom::AuthHostStubDispatch::Accept (impl=0xfc653e4, message=0xbe9eb988) at gen/components/arc/common/auth.mojom.cc:361
#8  0x09b35500 in mojo::internal::MultiplexRouter::ProcessIncomingMessage (this=0xd6ad540, message_wrapper=0xbe9eba50, client_call_behavior=<optimized out>, 
    current_task_runner=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/mojo/public/cpp/bindings/lib/multiplex_router.cc:880
#9  0x09b35294 in mojo::internal::MultiplexRouter::Accept (this=0xd6ad540, message=<optimized out>)
    at ../../../../../../../home/chrome-bot/chrome_root/src/mojo/public/cpp/bindings/lib/multiplex_router.cc:604
#10 0x09b347e6 in mojo::Connector::ReadSingleMessage (this=0xd6ad570, read_result=<optimized out>)
    at ../../../../../../../home/chrome-bot/chrome_root/src/mojo/public/cpp/bindings/lib/connector.cc:440
#11 mojo::Connector::ReadAllAvailableMessages (this=0xd6ad570) at ../../../../../../../home/chrome-bot/chrome_root/src/mojo/public/cpp/bindings/lib/connector.cc:469
#12 0x09b360ae in base::RepeatingCallback<void (unsigned int, mojo::HandleSignalsState const&)>::Run(unsigned int, mojo::HandleSignalsState const&) const & (args=..., args=..., 
    this=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/base/callback.h:94
#13 mojo::SimpleWatcher::OnHandleReady (this=0xfc16e40, watch_id=<optimized out>, result=0, state=...)
    at ../../../../../../../home/chrome-bot/chrome_root/src/mojo/public/cpp/system/simple_watcher.cc:276
#14 0x09b29718 in base::OnceCallback<void ()>::Run() && (this=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/base/callback.h:65
#15 base::debug::TaskAnnotator::RunTask (this=0xcbb2dc8, queue_function=0x9ef8bc1 "MessageLoop::PostTask", pending_task=0xbe9ebcb8)
    at ../../../../../../../home/chrome-bot/chrome_root/src/base/debug/task_annotator.cc:55
#16 0x09b29f48 in base::MessageLoop::RunTask (this=0xcbb2f20, pending_task=0xbe9ebcb8)
    at ../../../../../../../home/chrome-bot/chrome_root/src/base/message_loop/message_loop.cc:391
#17 0x09b2a582 in base::MessageLoop::DeferOrRunPendingTask (this=<optimized out>, pending_task=...)
    at ../../../../../../../home/chrome-bot/chrome_root/src/base/message_loop/message_loop.cc:403
#18 base::MessageLoop::DoWork (this=0xcbb2f20) at ../../../../../../../home/chrome-bot/chrome_root/src/base/message_loop/message_loop.cc:447
#19 0x09b2ab7c in base::MessagePumpLibevent::Run (this=0xcb9f030, delegate=0xcbb2f20)
    at ../../../../../../../home/chrome-bot/chrome_root/src/base/message_loop/message_pump_libevent.cc:220
#20 0x0689e540 in base::RunLoop::Run (this=0xbe9ebe78) at ../../../../../../../home/chrome-bot/chrome_root/src/base/run_loop.cc:114
#21 0x06645f30 in ChromeBrowserMainParts::MainMessageLoopRun (this=<optimized out>, result_code=0xcb6ef0c)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chrome_browser_main.cc:1939
#22 0x058705ea in content::BrowserMainLoop::RunMainMessageLoopParts (this=0xcb6ef00)
    at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main_loop.cc:1199
#23 0x05872664 in content::BrowserMainRunnerImpl::Run (this=0xcb6baf0) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main_runner.cc:140
#24 0x0586d7d6 in content::BrowserMain (parameters=...) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main.cc:46
#25 0x06637ea8 in content::ContentMainRunnerImpl::Run (this=0xcb6cf30) at ../../../../../../../home/chrome-bot/chrome_root/src/content/app/content_main_runner.cc:705
#26 0x0663dc22 in service_manager::Main (params=...) at ../../../../../../../home/chrome-bot/chrome_root/src/services/service_manager/embedder/main.cc:456
#27 0x06636fa0 in content::ContentMain (params=...) at ../../../../../../../home/chrome-bot/chrome_root/src/content/app/content_main.cc:19
#28 0x0541a068 in ChromeMain (argc=<optimized out>, argv=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/app/chrome_main.cc:130
#29 0xb67188a0 in __libc_start_main () from ./image/dir_3/lib/libc.so.6
#30 0x09bc70e0 in _start () at ../../../../../../../home/chrome-bot/chrome_root/src/base/message_loop/message_pump_libevent.cc:262

ARC++ kiosk is owned by Sergey

Do we have a targeted fix?  Understand the underlying issue?  Reminder that this is a blocker for the stable push.  Thx

I spent the whole day today trying to reproduce the issue and figure out the root cause.
I'll sync with MTV QA team soon and post an update here.

Do we know if kiosk mode is used much (at all) outside of tiger and fievel?

The stable release is running late here for ARC++ systems and we need to start moving forward soon, if we can hold back just the kiosk specific devices we should probably do so.

@shubhar, could you reply to #c9 or discuss with Bernie offline

I finally reproduced the issue and noticed some interesting stuff.

First of all, the crash happens immediately after GMS Core was stopped because of an update. Also, my crash stack trace on Chrome side is completely different from what Xiyuan got. See below:

Thread 0 (crashed)
 0  0x0
     r0 = 0x0d7ec3c0    r1 = 0x0000000a    r2 = 0x00000001    r3 = 0x00000000
     r4 = 0x098f7a50    r5 = 0xbec926bc    r6 = 0x00000001    r7 = 0xbec926b0
     r8 = 0x09533c00    r9 = 0x0a9d0d80   r10 = 0x0b7413c0   r12 = 0x0548db99
     fp = 0x0b7413f4    sp = 0xbec925f8    lr = 0x05d11b61    pc = 0x00000000
 1  chrome!(anonymous namespace)::do_free_with_callback(void*, void (*)(void*)) + 0xc6
 2  chrome!tc_malloc + 0x1e
 3  chrome!ash::wm::WindowState::Restore() + 0x3c
 4  chrome!aura::Window::RemoveChildImpl(aura::Window*, aura::Window*) + 0xbc
 5  chrome!aura::Window::RemoveChild(aura::Window*) + 0x56
 6  chrome!aura::Window::~Window() + 0x192
 7  chrome!aura::Window::NotifyWindowVisibilityChangedAtReceiver(aura::Window*, bool) + 0x1a6
 8  chrome!aura::Window::~Window() + 0x6
 9  chrome!views::Widget::CloseNow() + 0xdc
10  chrome!exo::ShellSurfaceBase::~ShellSurfaceBase() + 0xea
11  chrome!exo::ClientControlledShellSurface::~ClientControlledShellSurface() + 0x6
12  chrome!destroy_resource + 0x56
13  chrome!wl_resource_destroy + 0xc
14  libffi.so.6.0.2 + 0x414a
15  libffi.so.6.0.2 + 0x5fea
16  chrome!void exo::wayland::(anonymous namespace)::DestroyUserData<exo::Surface>(wl_resource*) + 0x24
17  libffi.so.6.0.2 + 0x47a1
18  chrome!wl_closure_invoke + 0x196
19  chrome!base::internal::CallbackBase::~CallbackBase() + 0x16
20  chrome!gpu::gles2::GLES2Implementation::RunIfContextNotLost(base::OnceCallback<void ()>) + 0x28
21  chrome!wl_os_recvmsg_cloexec + 0x14
22  chrome!wl_connection_read + 0xa6
23  chrome!viz::DisplayScheduler::UpdateHasPendingSurfaces() + 0x8c
24  libffi.so.6.0.2 + 0x5fea
25  libffi.so.6.0.2 + 0x5fea
26  chrome!tc_malloc + 0x1e
27  chrome!GlibcMallocHook + 0x18
28  chrome!wl_connection_demarshal + 0x88
29  libffi.so.6.0.2 + 0x5f7e
30  chrome!wl_client_connection_data + 0x1c6
31  chrome!_fini + 0x1cfd7c
32  chrome!wl_event_loop_dispatch + 0x48
33  chrome!gpu::CommandBufferProxyImpl::OnMessageReceived(IPC::Message const&) + 0xbc
34  chrome!(anonymous namespace)::do_free_with_callback(void*, void (*)(void*)) + 0xc6
35  chrome!_fini + 0x1209c6
36  chrome!gpu::GpuChannelHost::Listener::OnMessageReceived(IPC::Message const&) + 0x1f6
37  chrome!_fini + 0x1209c6
38  chrome!_fini + 0x1209c6
39  chrome!gpu::GpuChannelHost::Listener::OnMessageReceived(IPC::Message const&) + 0x1f6
40  chrome!base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) + 0x96
41  chrome!_fini + 0x1209c6
42  chrome!viz::DelayBasedTimeSource::PostNextTickTask(base::TimeTicks) + 0xfe
43  chrome!_fini + 0x1209c6
44  chrome!_fini + 0x1209c6
45  chrome!viz::DelayBasedTimeSource::PostNextTickTask(base::TimeTicks) + 0xfe
46  chrome!base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) + 0x96
47  chrome!gpu::GpuChannelHost::Listener::OnMessageReceived(IPC::Message const&) + 0x1f6
48  chrome!mojo::SimpleWatcher::Context::Notify(unsigned int, MojoHandleSignalsState, unsigned int) + 0x98
49  chrome!gpu::GpuChannelHost::Listener::OnMessageReceived(IPC::Message const&) + 0x1f6
50  chrome!base::MessageLoop::RunTask(base::PendingTask*) + 0x208
51  chrome!viz::DelayBasedTimeSource::PostNextTickTask(base::TimeTicks) + 0xfe
52  chrome!viz::DelayBasedTimeSource::PostNextTickTask(base::TimeTicks) + 0xfe
53  chrome!base::PendingTask::operator=(base::PendingTask&&) + 0xa
54  chrome!_fini + 0x1cfd7c
55  chrome!__divdi3 + 0x2e
56  chrome!__divmoddi4 + 0xe
57  chrome!_fini + 0x1cfd7c
58  chrome!exo::wayland::Server::Dispatch(base::TimeDelta) + 0x28
59  chrome!ash::WaylandServerController::WaylandWatcher::OnFileCanReadWithoutBlocking(int) + 0xe
60  chrome!base::MessagePumpLibevent::OnLibeventNotification(int, short, void*) + 0xb6
61  chrome!base::TimeTicks::Now() + 0x18
62  chrome!mojo::SimpleWatcher::Context::Notify(unsigned int, MojoHandleSignalsState, unsigned int) + 0x98
63  chrome!base::MessageLoop::DoDelayedWork(base::TimeTicks*) + 0x52
64  chrome!_fini + 0x16477c
65  chrome!_fini + 0x1e056f
66  chrome!viz::DisplayScheduler::ScheduleBeginFrameDeadline() + 0x21a
67  chrome!tc_realloc + 0x7a
68  chrome!viz::DelayBasedTimeSource::PostNextTickTask(base::TimeTicks) + 0xfe
69  chrome!viz::DelayBasedTimeSource::PostNextTickTask(base::TimeTicks) + 0xfe
70  libc-2.23.so + 0x985dd
71  chrome!base::MessagePumpLibevent::WatchFileDescriptor(int, bool, int, base::MessagePumpLibevent::FileDescriptorWatcher*, base::MessagePumpLibevent::Watcher*) + 0xae
72  chrome!event_base_loop + 0x37a
73  chrome!base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) + 0xf8
74  chrome!base::RunLoop::Run() + 0x28
75  chrome!ChromeBrowserMainParts::MainMessageLoopRun(int*) + 0x96
76  chrome!base::SampleVectorBase::Accumulate(int, int) + 0x30
77  chrome!__aeabi_ldivmod + 0xa
78  chrome!_fini + 0x6a616e
79  chrome!_fini + 0x1197b5
80  chrome!content::BrowserMainLoop::RunMainMessageLoopParts() + 0x34
81  chrome!std::__1::__tree<std::__1::__value_type<base::trace_event::TraceLog::AsyncEnabledStateObserver*, base::trace_event::TraceLog::RegisteredAsyncObserver>, std::__1::__map_value_compare<base::trace_event::TraceLog::AsyncEnabledStateObserver*, std::__1::__value_type<base::trace_event::TraceLog::AsyncEnabledStateObserver*, base::trace_event::TraceLog::RegisteredAsyncObserver>, std::__1::less<base::trace_event::TraceLog::AsyncEnabledStateObserver*>, true>, std::__1::allocator<std::__1::__value_type<base::trace_event::TraceLog::AsyncEnabledStateObserver*, base::trace_event::TraceLog::RegisteredAsyncObserver> > >::destroy(std::__1::__tree_node<std::__1::__value_type<base::trace_event::TraceLog::AsyncEnabledStateObserver*, base::trace_event::TraceLog::RegisteredAsyncObserver>, void*>*) + 0x42
82  chrome!content::BrowserMainRunnerImpl::Run() + 0xa
83  chrome!content::BrowserMain(content::MainFunctionParams const&) + 0x112
84  chrome!base::CommandLine::GetSwitchValueASCII(base::BasicStringPiece<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > > const&) const + 0x38
85  chrome!content::ContentMainRunnerImpl::Run() + 0xa6
86  chrome!service_manager::Main(service_manager::MainParams const&) + 0x590
87  chrome!_fini + 0x6a606e
88  chrome!(anonymous namespace)::do_free_with_callback(void*, void (*)(void*)) + 0xc6
89  chrome!operator new(unsigned int) + 0x18
90  chrome!_fini + 0x60e08c

My assumption and observation is that it happens only on the very first ARC++ Kiosk start, when session is provisioned and GMSCore is updated.
All subsequent kiosk auto-launches should successfully launch the app that won't be closed after that.

I'm leaving office now, so leaving it to QA team to get more repros, crash dumps/logs and check whether only the first launch is affected.

I was able to reproduce this bug on a different the device. I tried different steps to reproduce this bug. Out of ~20 times I was able to reproduce this one time. 

Initially the application that I tried to auto launch in kiosk mode was Angry Birds, it seemed pretty stable. The initial launch was working properly and all the subsequent reboots were properly launching the app. I would cancel the auto launch of the first application enabled in c panel(angry birds) and initialize another application to see if this would reproduce the bug and it didn't.

These are the steps I took before the bug occured again.
1.Go through OOBE on device once again
2.Enroll in enterprise mode
3.Change the application automatically launched in c panel
4.Wait for application to initialize.

I am attaching two separate bug reports of the two different times this has bug has occured. 

coreDump

https://drive.google.com/file/d/1XTmJGnllNJW4VIHzYb-nmlc6qgootS_Q/view?usp=sharing

Deleted: debug-logs_20180213-152818.tgz 137 KB

debug-logs_20180213-152818.tgz 137 KB Download

Deleted: logcat.txt 222 KB

logcat.txt 222 KB View Download

Logs for the second crash

coreDumps

https://drive.google.com/file/d/1Hjq29Ra1fhArD4b4rD8ohOkghNB6B_tU/view?usp=sharing

Deleted: logcat.txt 222 KB

logcat.txt 222 KB View Download

Deleted: debug-logs_20180213-155938.tgz 223 KB

debug-logs_20180213-155938.tgz 223 KB Download

crash in #13 and #14 (core.chrome.949/5), both have the same stack as what I saw in #4.

My result from today are two crashes on M64-10176.72.0 (newer build). Core dumps are: 
https://drive.google.com/open?id=1tOM1738k1S0poniw-kGyKr94e-9LoeWr
https://drive.google.com/open?id=1l0h51xe6cMnUw344XrJgYk9h9ndFOjKb

For yet unknown reason I failed to get stack traces from them...

Anyway, I think the issue shouldn't really block Chrome OS stable push for ARC++ board, maybe only except to the ones that are used for ARC++ Kiosk (tiger, fievel?)

I'm not planning to block on this bug given the impact numbers.  I can reconsider if we can identify a specific board where the problem lies (and block that board).  Removing the stable blocker for now.

I consistently getting different crash stack traces for Chrome:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00000000 in ?? ()
[Current thread is 1 (LWP 3345)]
(gdb) bt
#0  0x00000000 in ?? ()
#1  0x04f57cb8 in ash::wm::ClientControlledState::HandleTransitionEvents (this=0xc2d1fc0, window_state=0xb159aa0, event=0xbeede6e4)
    at ../../../../../../../home/chrome-bot/chrome_root/src/ash/wm/client_controlled_state.cc:48
#2  0x04f71f3a in ash::wm::WindowState::OnWMEvent (event=0x79ea23c <vtable for ash::wm::WMEvent+8>, this=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/ash/wm/window_state.cc:275
#3  ash::wm::WindowState::Restore (this=0xb159aa0) at ../../../../../../../home/chrome-bot/chrome_root/src/ash/wm/window_state.cc:239
#4  0x04634252 in aura::Window::RemoveChildImpl (this=0x818de40, child=0xaf52600, new_parent=0x0) at ../../../../../../../home/chrome-bot/chrome_root/src/ui/aura/window.cc:845
#5  0x046330f0 in aura::Window::RemoveChild (this=0x818de40, child=0xaf52600) at ../../../../../../../home/chrome-bot/chrome_root/src/ui/aura/window.cc:408
#6  0x04632e34 in aura::Window::~Window (this=0xaf52600) at ../../../../../../../home/chrome-bot/chrome_root/src/ui/aura/window.cc:125
#7  0x046331ae in aura::Window::~Window (this=0xc2d03e0) at ../../../../../../../home/chrome-bot/chrome_root/src/ui/aura/window.cc:80
#8  0x048bdf1e in views::Widget::CloseNow (this=0x9a45c30) at ../../../../../../../home/chrome-bot/chrome_root/src/ui/views/widget/widget.cc:607
#9  0x02e9f690 in exo::ShellSurfaceBase::~ShellSurfaceBase (this=0x9edac00) at ../../../../../../../home/chrome-bot/chrome_root/src/components/exo/shell_surface_base.cc:315
#10 0x02e957a6 in exo::ClientControlledShellSurface::~ClientControlledShellSurface (this=0xc2d03e0) at ../../../../../../../home/chrome-bot/chrome_root/src/components/exo/client_controlled_shell_surface.cc:184
#11 0x04ff5b30 in destroy_resource (element=0xac83fc0, data=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/third_party/wayland/src/src/wayland-server.c:677
#12 0x04ff5aa6 in wl_resource_destroy (resource=0xc2d03e0) at ../../../../../../../home/chrome-bot/chrome_root/src/third_party/wayland/src/src/wayland-server.c:692
#13 0xa997414c in ffi_call_VFP () at /build/veyron_fievel/tmp/portage/dev-libs/libffi-3.1-r4/work/libffi-3.1/src/arm/sysv.S:377
#14 0xa99747a2 in ffi_call (cif=0xbeede9f8, fn=<optimized out>, rvalue=0x0, avalue=<optimized out>) at ../libffi-3.1/src/arm/ffi.c:344
#15 0x04ff73bc in wl_closure_invoke (closure=<optimized out>, flags=<optimized out>, target=<optimized out>, opcode=0, data=0x9993ee0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/third_party/wayland/src/src/connection.c:935
#16 0x04ff5960 in wl_client_connection_data (fd=<optimized out>, mask=<optimized out>, data=<optimized out>)
    at ../../../../../../../home/chrome-bot/chrome_root/src/third_party/wayland/src/src/wayland-server.c:408
#17 0x04ff51ca in wl_event_loop_dispatch (loop=0x8501c60, timeout=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/third_party/wayland/src/src/event-loop.c:423
#18 0x02ea9902 in exo::wayland::Server::Dispatch (this=<optimized out>, timeout=...) at ../../../../../../../home/chrome-bot/chrome_root/src/components/exo/wayland/server.cc:4626
#19 0x02e93e48 in ash::WaylandServerController::WaylandWatcher::OnFileCanReadWithoutBlocking (this=0x8501d80, fd=-1091704608)
    at ../../../../../../../home/chrome-bot/chrome_root/src/ash/wayland/wayland_server_controller.cc:34
#20 0x06bd18e4 in base::MessagePumpLibevent::OnLibeventNotification (fd=12, flags=2, context=0x8501d84) at ../../../../../../../home/chrome-bot/chrome_root/src/base/message_loop/message_pump_libevent.cc:97
#21 0x06bd9f3e in event_process_active (base=0x7fda800) at ../../../../../../../home/chrome-bot/chrome_root/src/base/third_party/libevent/event.c:381
#22 event_base_loop (base=0x7fda800, flags=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/base/third_party/libevent/event.c:521
#23 0x06bd1abc in base::MessagePumpLibevent::Run (this=0x7fff480, delegate=0x800df20) at ../../../../../../../home/chrome-bot/chrome_root/src/base/message_loop/message_pump_libevent.cc:224
#24 0x03945540 in base::RunLoop::Run (this=0xbeedeec8) at ../../../../../../../home/chrome-bot/chrome_root/src/base/run_loop.cc:114
#25 0x036ecf30 in ChromeBrowserMainParts::MainMessageLoopRun (this=<optimized out>, result_code=0x7fc9f0c) at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chrome_browser_main.cc:1939
#26 0x029175ea in content::BrowserMainLoop::RunMainMessageLoopParts (this=0x7fc9f00) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main_loop.cc:1199
#27 0x02919664 in content::BrowserMainRunnerImpl::Run (this=0x7fc6ae0) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main_runner.cc:140
#28 0x029147d6 in content::BrowserMain (parameters=...) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main.cc:46
#29 0x036deea8 in content::ContentMainRunnerImpl::Run (this=0x7fc7e70) at ../../../../../../../home/chrome-bot/chrome_root/src/content/app/content_main_runner.cc:705
#30 0x036e4c22 in service_manager::Main (params=...) at ../../../../../../../home/chrome-bot/chrome_root/src/services/service_manager/embedder/main.cc:456
#31 0x036ddfa0 in content::ContentMain (params=...) at ../../../../../../../home/chrome-bot/chrome_root/src/content/app/content_main.cc:19
#32 0x024c1068 in ChromeMain (argc=<optimized out>, argv=<optimized out>) at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/app/chrome_main.cc:130
#33 0xa97db8a0 in __libc_start_main (main=0x24c0e01 <main(int, char const**)>, argc=27, argv=0xbeedf484, init=<optimized out>, fini=0x6e5e609 <__libc_csu_fini>, rtld_fini=0xa9e55d8d <_dl_fini>, 
    stack_end=0xbeedf484) at libc-start.c:289
#34 0x06c6e0e0 in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Core dump: https://drive.google.com/open?id=17Mg9O5N22jqM1ewJ_1QvOjl95oCLuyEl

Deleted: arc-crash-logcat.txt 76.6 KB

arc-crash-logcat.txt 76.6 KB View Download

Looks like something crashes in Chrome UI when GMS Core is updated and Activities are killed: 

02-15 12:48:55.659    73   102 I ActivityManager: Killing 2110:com.android.vending/u0a18 (adj 100): stop com.google.android.gms
02-15 12:48:55.659    73   102 D ActivityManager: cleanUpApplicationRecord -- 2110
02-15 12:48:55.660    73   102 W ActivityManager: Scheduling restart of crashed service com.android.vending/com.google.android.finsky.billing.iab.InAppBillingService in 180997ms
02-15 12:48:55.660    73   104 W libprocessgroup: failed to open /acct/uid_10018/pid_2110/cgroup.procs: Permission denied
02-15 12:48:55.660    73   102 I ActivityManager: Killing 1795:com.google.android.gms:car/u0a14 (adj 904): stop com.google.android.gms
02-15 12:48:55.660    73   102 D ActivityManager: cleanUpApplicationRecord -- 1795
02-15 12:48:55.660    73   104 W libprocessgroup: failed to open /acct/uid_10014/pid_1795/cgroup.procs: Permission denied
02-15 12:48:55.660    73   102 I ActivityManager: Killing 1989:com.rovio.angrybirds/u0a51 (adj 0): stop com.google.android.gms
02-15 12:48:55.661    73   102 D ActivityManager: cleanUpApplicationRecord -- 1989

Assigning to Mitsuru to triage on Chrome UI side and guess why Chrome might crash in such a case.

I little bit more info.
Looks like ClientControlledShellSurface is destroyed before ClientControlledStateDelegate::HandleWindowStateRequest() is called that tries to call a function is the destroyed ClientControlledShellSurface* shell_surface_;

[1278:1278:0215/143158.879880:ERROR:client_controlled_shell_surface.cc(188)] ~ClientControlledShellSurface() this: 0x1836a180
[1278:1278:0215/143158.889708:ERROR:client_controlled_shell_surface.cc(79)] HandleWindowStateRequest() shell_surface_: 0x1836a180

https://cs.chromium.org/chromium/src/components/exo/client_controlled_shell_surface.cc?l=79&rcl=2ae400b023395688c5e68383e3eacca49213b3bb

I checked that if do not call shell_surface_->OnWindowStateChangeEvent (see link before), Chrome won't crash in that case and ARC container will continue to work properly.

However, the kiosk app won't be restarted, due to a simple bug. I'll have a very simple one-line fix in a few minutes, so that the app will be restarted in that case (GMS Core update).

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/00348304f519c4e971cba761b67e23b900c311d6

commit 00348304f519c4e971cba761b67e23b900c311d6
Author: Sergey Poromov <poromov@chromium.org>
Date: Thu Feb 15 17:21:19 2018

Fix task creation check in ArcKioskAppService.

OnTaskCreated()'s intent parameter has slightly more information
than in AppInfo.
Due to that check existence, task_id_ was never remembered and
the kiosk app was not restarted on crash/termination.
This change won't negatively affect ARC Kiosk functionality as starting
by an intent is not supported anyway.

BUG=812594
BUG= 811398 

Test=Manual, check that app is properly restarted after termination.

Change-Id: I51523545833744aebc1f1c7dfe9c7aacf7414484
Reviewed-on: https://chromium-review.googlesource.com/922101
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537056}
[modify] https://crrev.com/00348304f519c4e971cba761b67e23b900c311d6/chrome/browser/chromeos/app_mode/arc/arc_kiosk_app_service.cc

Requesting merge for a one-line CL fix that touches only ARC Kiosk code. It fixes ARC Kiosk relaunch in case of crash/termination.

I'm out with a family emergency; josafat@ is covering.  Small change, but that doesn't mean it can't have a large impact.  Is this the fix referenced in #22?  Is this a full fix, or partial for some edge cases?  Note that we're into M64 stable so any merges will need a broad impact and verified fix.  Email on this topic didn't uncover a broad scope.

The main bug that leads Chrome to crash from #21 is not yet fixed - this bug is assigned to oshima@

However, even without the crash, ARC Kiosk won't work properly, as my fix from comment #23 will also be needed.

IMO, if Mitsuru will manage to fix the main Chrome crash issue, than my fix should also be merged and ARC Kiosk issue will be fully resolved. Otherwise, my change won't have much impact.

Re scope: the issue affects only ARC Kiosk users, their first launch experience. Per logs, there are currently not so many ARC Kiosk devices - around 200-300 weekly. However, it will affect all new customers adopting ARC Kiosk in M64. I don't know any data about their amount though.

Assuming this is Pinned app, this is probably due to this line:

https://cs.chromium.org/chromium/src/ash/wm/screen_pinning_controller.cc?rcl=223fa7dcfbdc876bcd3a0bc5bc70fde78a44e4f6&l=236

hidehiko@, do you remember why this is necessary?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/09b2a46b75198adfc25ccfb45b17f64b1bdc0f81

commit 09b2a46b75198adfc25ccfb45b17f64b1bdc0f81
Author: Sergey Poromov <poromov@chromium.org>
Date: Tue Feb 20 20:04:48 2018

Fix task creation check in ArcKioskAppService.

OnTaskCreated()'s intent parameter has slightly more information
than in AppInfo.
Due to that check existence, task_id_ was never remembered and
the kiosk app was not restarted on crash/termination.
This change won't negatively affect ARC Kiosk functionality as starting
by an intent is not supported anyway.

BUG=812594
BUG= 811398 

Test=Manual, check that app is properly restarted after termination.

Change-Id: I51523545833744aebc1f1c7dfe9c7aacf7414484
Reviewed-on: https://chromium-review.googlesource.com/922101
Reviewed-by: Xiyuan Xia <xiyuan@chromium.org>
Commit-Queue: Sergey Poromov <poromov@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#537056}(cherry picked from commit 00348304f519c4e971cba761b67e23b900c311d6)
Reviewed-on: https://chromium-review.googlesource.com/927241
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/branch-heads/3325@{#511}
Cr-Branched-From: bc084a8b5afa3744a74927344e304c02ae54189f-refs/heads/master@{#530369}
[modify] https://crrev.com/09b2a46b75198adfc25ccfb45b17f64b1bdc0f81/chrome/browser/chromeos/app_mode/arc/arc_kiosk_app_service.cc

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/64bf482feb86ae02503c588cad1cb56e46c31b1d

commit 64bf482feb86ae02503c588cad1cb56e46c31b1d
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Thu Feb 22 00:03:53 2018

Delete delegates in WindowState when window is being destroyed

Pinned app can request restore during destruction, (which itself
shouldn't happen), but the windowstate should also have a safe guard
by deleting delegate when being deleted.

BUG= 811398 
TEST=covered by unit tests

Change-Id: I4de6608e97dcf9e48531d31b07a530c10ef68978
Reviewed-on: https://chromium-review.googlesource.com/929315
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#538262}
[modify] https://crrev.com/64bf482feb86ae02503c588cad1cb56e46c31b1d/ash/wm/client_controlled_state.cc
[modify] https://crrev.com/64bf482feb86ae02503c588cad1cb56e46c31b1d/ash/wm/client_controlled_state.h
[modify] https://crrev.com/64bf482feb86ae02503c588cad1cb56e46c31b1d/ash/wm/client_controlled_state_unittest.cc
[modify] https://crrev.com/64bf482feb86ae02503c588cad1cb56e46c31b1d/ash/wm/screen_pinning_controller.cc
[modify] https://crrev.com/64bf482feb86ae02503c588cad1cb56e46c31b1d/ash/wm/window_state.cc
[modify] https://crrev.com/64bf482feb86ae02503c588cad1cb56e46c31b1d/ash/wm/window_state.h

Thanks for the fix! Should it be merged back into M65 at least?

This bug requires manual review: We are only 10 days from stable.
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), bhthompson@(ChromeOS), govind@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Looks like Bernie (bhthompson@) is OOO.
Could someone else approve it as we need this fix in M65 before stable cut?

+josafat@ for M65 merge review.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/2fc454fa9ab4c7cfb44afbd5377dbf99428466e6

commit 2fc454fa9ab4c7cfb44afbd5377dbf99428466e6
Author: Mitsuru Oshima <oshima@chromium.org>
Date: Tue Feb 27 19:42:17 2018

Delete delegates in WindowState when window is being destroyed

Pinned app can request restore during destruction, (which itself
shouldn't happen), but the windowstate should also have a safe guard
by deleting delegate when being deleted.

BUG= 811398 
TEST=covered by unit tests

Change-Id: I4de6608e97dcf9e48531d31b07a530c10ef68978
Reviewed-on: https://chromium-review.googlesource.com/929315
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Mitsuru Oshima <oshima@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#538262}(cherry picked from commit 64bf482feb86ae02503c588cad1cb56e46c31b1d)
Reviewed-on: https://chromium-review.googlesource.com/939921
Reviewed-by: Mitsuru Oshima <oshima@chromium.org>
Cr-Commit-Position: refs/branch-heads/3325@{#609}
Cr-Branched-From: bc084a8b5afa3744a74927344e304c02ae54189f-refs/heads/master@{#530369}
[modify] https://crrev.com/2fc454fa9ab4c7cfb44afbd5377dbf99428466e6/ash/wm/client_controlled_state.cc
[modify] https://crrev.com/2fc454fa9ab4c7cfb44afbd5377dbf99428466e6/ash/wm/client_controlled_state.h
[modify] https://crrev.com/2fc454fa9ab4c7cfb44afbd5377dbf99428466e6/ash/wm/client_controlled_state_unittest.cc
[modify] https://crrev.com/2fc454fa9ab4c7cfb44afbd5377dbf99428466e6/ash/wm/screen_pinning_controller.cc
[modify] https://crrev.com/2fc454fa9ab4c7cfb44afbd5377dbf99428466e6/ash/wm/window_state.cc
[modify] https://crrev.com/2fc454fa9ab4c7cfb44afbd5377dbf99428466e6/ash/wm/window_state.h

I am still seeing this behavior on veyron fievel on M66 ToT(10461.0.0/67.0.3362.0). Except now the device is restarting itself after the crash. I am trying to initialize Google Hangouts

link to core dump files

https://drive.google.com/drive/folders/1TW9LCSiWhCqPhl9eOH2hO9qdnGE3BiNP?usp=sharing

mov link

https://drive.google.com/file/d/1esEmQKy__hFw0OBqFJZJKYumGL78Lmyw/view?usp=sharing

Deleted: debug-logs_20180305-132825.tgz 398 KB

debug-logs_20180305-132825.tgz 398 KB Download

Deleted: logcatM66.txt 22.1 KB

logcatM66.txt 22.1 KB View Download

Small note, I am able to launch arc applications while in consumer mode on M66 ToT(10461.0.0/67.0.3362.0)

This could be related to https://b.corp.google.com/issues/74123622. 
@vaandres, could you retest after this is synced.. 

do you have a link to crash report? I've been trying to get stack, but am blocked by  crbug.com/818865  now.

The logcat indicates that ARC was unable to boot.  vaandres@, can I take a look at your machine?


03-05 21:19:31.366    22    40 W wayland-service: Detected a fatal Wayland error. Restarting connection.
03-05 21:19:31.366    22    40 E wayland-service: WaylandCreateSocket -- Unable to connect (111)
03-05 21:19:31.367    22    40 W wayland-service: Wayland not available. Unable to connect to server.
03-05 21:19:31.367    22    40 W wayland-service: No Wayland connection possible. Will retry...

"WaylandCreateSocket -- Unable to connect (111)" happens when chrome crashes.

I finally re-created my chroot. I looked at the first two coredumps in #38: 989 and 2812. The looks the same and 2812 has complete stack. And it is no longer the crash thas oshima@ fixed.

Here is the crash stack of core.chrome.2812:
====
Core was generated by `/opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepfl'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  std::__1::unique_ptr<chromeos::input_method::ImeKeyboard, std::__1::default_delete<chromeos::input_method::ImeKeyboard> >::get (this=0xb8)
    at /usr/bin/../include/c++/v1/memory:2587
2587        _LIBCPP_INLINE_VISIBILITY pointer get() const _NOEXCEPT {return __ptr_.first();}
[Current thread is 1 (LWP 2812)]
(gdb) bt
#0  std::__1::unique_ptr<chromeos::input_method::ImeKeyboard, std::__1::default_delete<chromeos::input_method::ImeKeyboard> >::get (this=0xb8)
    at /usr/bin/../include/c++/v1/memory:2587
#1  chromeos::input_method::InputMethodManagerImpl::GetImeKeyboard (this=0x0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/input_method/input_method_manager_impl.cc:1135
#2  0x034aa90a in policy::AppInstallEventLogManagerWrapper::CreateManager (this=0x99573c0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/policy/app_install_event_log_manager_wrapper.cc:63
#3  0x034aa8be in policy::AppInstallEventLogManagerWrapper::EvaluatePref (this=0x99573c0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/policy/app_install_event_log_manager_wrapper.cc:74
#4  0x034aa63c in policy::AppInstallEventLogManagerWrapper::Init (this=0x99573c0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/policy/app_install_event_log_manager_wrapper.cc:55
#5  policy::AppInstallEventLogManagerWrapper::CreateForProfile (profile=<optimized out>)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/policy/app_install_event_log_manager_wrapper.cc:28
#6  0x034505ae in chromeos::(anonymous namespace)::StartUserSession (user_profile=<optimized out>, login_user_id=...)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/login/session/chrome_session_manager.cc:124
#7  0x03450266 in chromeos::ChromeSessionManager::Initialize (this=<optimized out>, parsed_command_line=..., profile=0x90ec8c0, is_running_test=<optimized out>)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/login/session/chrome_session_manager.cc:219
#8  0x033b99a4 in chromeos::ChromeBrowserMainPartsChromeos::PostProfileInit (this=0x8d919a0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/chrome_browser_main_chromeos.cc:968
#9  0x03b8ead8 in ChromeBrowserMainParts::PreMainMessageLoopRunImpl (this=0x8d919a0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chrome_browser_main.cc:1860
#10 0x03b8e3e4 in ChromeBrowserMainParts::PreMainMessageLoopRun (this=0x8d919a0) at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chrome_browser_main.cc:1440
#11 0x033b9010 in chromeos::ChromeBrowserMainPartsChromeos::PreMainMessageLoopRun (this=0x8d919a0)
    at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/browser/chromeos/chrome_browser_main_chromeos.cc:710
#12 0x02d14cea in content::BrowserMainLoop::PreMainMessageLoopRun (this=0x8da8d80)
    at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main_loop.cc:1087
#13 0x02f7a83c in base::RepeatingCallback<int ()>::Run() const & (this=0x8e4db78) at ../../../../../../../home/chrome-bot/chrome_root/src/base/callback.h:124
#14 content::StartupTaskRunner::RunAllTasksNow (this=0x8e24a60) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/startup_task_runner.cc:45
#15 0x02d13c1e in content::BrowserMainLoop::CreateStartupTasks (this=0x8da8d80) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main_loop.cc:970
#16 0x02d16836 in content::BrowserMainRunnerImpl::Initialize (this=<optimized out>, parameters=...)
    at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main_runner.cc:139
#17 0x02d122de in content::BrowserMain (parameters=...) at ../../../../../../../home/chrome-bot/chrome_root/src/content/browser/browser_main.cc:42
#18 0x03b8237e in content::ContentMainRunnerImpl::Run (this=0x8d81e40) at ../../../../../../../home/chrome-bot/chrome_root/src/content/app/content_main_runner.cc:703
#19 0x03b8831a in service_manager::Main (params=...) at ../../../../../../../home/chrome-bot/chrome_root/src/services/service_manager/embedder/main.cc:453
#20 0x03b81506 in content::ContentMain (params=...) at ../../../../../../../home/chrome-bot/chrome_root/src/content/app/content_main.cc:19
#21 0x0273bddc in ChromeMain (argc=29, argv=0xbef563b4) at ../../../../../../../home/chrome-bot/chrome_root/src/chrome/app/chrome_main.cc:101
#22 0xb1f398a0 in __libc_start_main () from ./image/dir_3/lib/libc.so.6
#23 0x0273bc88 in _start () at ../../../../../../../home/chrome-bot/chrome_root/src/base/bind_internal.h:668

AppInstallEventLogManagerWrapper is used to log events related to ARC++ app installs. It attaches to a lot of subsystems that are singletons with ill-defined lifetimes. I am not entirely surprised this can blow up in some start-up paths.

If this is breaking in kiosk only, the easiest way is to disable the AppInstallEventLogManagerWrapper for kiosk. We are not planning to collect events for kiosks for the moment anyway.

Unfortunately, I cannot investigate right now as it is EOD here.

It is indeed crashing during login.

Veyron Tiger is able to properly initialize applications using M65 beta(10323.50.0 	65.0.3325.118)

Fix under review: https://chromium-review.googlesource.com/c/chromium/src/+/952904

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a1fadc8f1dd934ebf94554ae0821a35060a61c66

commit a1fadc8f1dd934ebf94554ae0821a35060a61c66
Author: Bartosz Fabianowski <bartfab@chromium.org>
Date: Thu Mar 08 22:54:26 2018

Start app push-install logging for regular users only

App push-install log uploads are authenticated with the user's
DMToken. It makes no sense to collect logs for any other users
(e.g. kiosks, public sessions) as we would be unable to upload
them anyway.

Plus, trying to instantiate the logging framework in kiosk
sessions leads to crashes as some singletons come up in an
unexpected order.

Bug:  811398 
Test: Manual
Change-Id: I827f3cd85accb423ac61bc5f6450753e9c6418cf
Reviewed-on: https://chromium-review.googlesource.com/952904
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Bartosz Fabianowski <bartfab@chromium.org>
Cr-Commit-Position: refs/heads/master@{#541915}
[modify] https://crrev.com/a1fadc8f1dd934ebf94554ae0821a35060a61c66/chrome/browser/chromeos/login/session/chrome_session_manager.cc
[modify] https://crrev.com/a1fadc8f1dd934ebf94554ae0821a35060a61c66/chrome/browser/chromeos/login/session/user_session_manager.cc

Requesting merge of https://chromium-review.googlesource.com/952904 to M66.

Your change meets the bar and is auto-approved for M66. Please go ahead and merge the CL to branch 3359 manually. Please contact milestone owner if you have questions.
Owners: cmasso@(Android), cmasso@(iOS), josafat@(ChromeOS), abdulsyed@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/7aa9b43c7c213aada0bb8476736c93a80c1b5c10

commit 7aa9b43c7c213aada0bb8476736c93a80c1b5c10
Author: Sergey Poromov <poromov@chromium.org>
Date: Wed Mar 14 12:23:21 2018

Start app push-install logging for regular users only

App push-install log uploads are authenticated with the user's
DMToken. It makes no sense to collect logs for any other users
(e.g. kiosks, public sessions) as we would be unable to upload
them anyway.

Plus, trying to instantiate the logging framework in kiosk
sessions leads to crashes as some singletons come up in an
unexpected order.

TBR=bartfab@chromium.org

(cherry picked from commit a1fadc8f1dd934ebf94554ae0821a35060a61c66)

Bug:  811398 
Test: Manual
Change-Id: I827f3cd85accb423ac61bc5f6450753e9c6418cf
Reviewed-on: https://chromium-review.googlesource.com/952904
Reviewed-by: Achuith Bhandarkar <achuith@chromium.org>
Commit-Queue: Bartosz Fabianowski <bartfab@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#541915}
Reviewed-on: https://chromium-review.googlesource.com/962025
Reviewed-by: Sergey Poromov <poromov@chromium.org>
Cr-Commit-Position: refs/branch-heads/3359@{#231}
Cr-Branched-From: 66afc5e5d10127546cc4b98b9117aff588b5e66b-refs/heads/master@{#540276}
[modify] https://crrev.com/7aa9b43c7c213aada0bb8476736c93a80c1b5c10/chrome/browser/chromeos/login/session/chrome_session_manager.cc
[modify] https://crrev.com/7aa9b43c7c213aada0bb8476736c93a80c1b5c10/chrome/browser/chromeos/login/session/user_session_manager.cc

Using today's build(10452.14.0, 66.0.3359.35 ), I tried to auto launch and manual launch a couple of ARC applications, once the application is initialized, the device gets stuck in "Initializing application window" screen. I also tested on M67 ToT (10494.0.0 67.0.3369.0) and the fix works fine, applications are initialized and are working properly.

Attaching logs for M66 10452.14.0, 66.0.3359.35

Deleted: logcat.txt 669 KB

logcat.txt 669 KB View Download

Deleted: debug-logs_20180316-115758.tgz 195 KB

debug-logs_20180316-115758.tgz 195 KB Download

Deleted: varLog.tar 990 KB

varLog.tar 990 KB Download

Moving to new bug/thread

https://bugs.chromium.org/p/chromium/issues/detail?id=822864