Fixed
Status Update
No update yet.
Comments
zm...@google.com
This means your GPU process keeps failing launch.
If you can reproduce this locally, please attach a debug to GPU process and figure out why it fails at launch time.
If you can reproduce this locally, please attach a debug to GPU process and figure out why it fails at launch time.
kh...@chromium.org
> If you can reproduce this locally
Reproduces 100% of the time for me.
> please attach a debug to GPU process and figure out why it fails at launch time.
I'm unfamiliar with how to do this. Can you provide some instructions on what I should do? Thanks!
Reproduces 100% of the time for me.
> please attach a debug to GPU process and figure out why it fails at launch time.
I'm unfamiliar with how to do this. Can you provide some instructions on what I should do? Thanks!
jo...@chromium.org
[gpu-triage] Owner assigned, so updating status.
zm...@google.com
1) In order to catch the GPU process crash, you need to run Chrome with --gpu-starup-dialog. That will allow Chrome to pause at GPU process launch time, and print out the GPU process id. Then you can attach a gdb debugger to that process id, and step through GPU process initialization code, and see where it fails.
2) The other thing you can try is go to about:crashes, and see if there are GPU process crashes there. If yes, please share the crash hash with us and we could take a look.
3) You can also run with --disable-gpu-sandbox and see if that fixes the problem. If yes, then we know it's some sandbox issue that prevents GPU process from launching.
2) The other thing you can try is go to about:crashes, and see if there are GPU process crashes there. If yes, please share the crash hash with us and we could take a look.
3) You can also run with --disable-gpu-sandbox and see if that fixes the problem. If yes, then we know it's some sandbox issue that prevents GPU process from launching.
kh...@chromium.org
> 1) In order to catch the GPU process crash, you need to run Chrome with --gpu-starup-dialog. That will allow Chrome to pause at GPU process launch time, and print out the GPU process id. Then you can attach a gdb debugger to that process id, and step through GPU process initialization code, and see where it fails.
I tried this by setting the flag in the /etc/chrome_dev.conf file, but once I set the flag, my device would not start up at all anymore. It would freeze on the white screen with the Chrome logo. It would not reboot again until I recovered the device. Is there another way I'm supposed to do this>
> 2) The other thing you can try is go to about:crashes, and see if there are GPU process crashes there. If yes, please share the crash hash with us and we could take a look.
I can't get Chrome to start up at all, so I can't go to about:crashes.
> 3) You can also run with --disable-gpu-sandbox and see if that fixes the problem. If yes, then we know it's some sandbox issue that prevents GPU process from launching.
Didn't get to this because of the note to #1.
Another note: I flashed to an older CrOS version from a few days back then flashed ToT Chrome and got this same issue. It does appear to be a regression in Chrome, not Chrome OS. I synced to ToT yesterday and was successfully able to deploy Chrome to my device via the Simple Chrome flow. With today's ToT, I run into thishttps://crbug.com/chromium/100% of the time.
I tried this by setting the flag in the /etc/chrome_dev.conf file, but once I set the flag, my device would not start up at all anymore. It would freeze on the white screen with the Chrome logo. It would not reboot again until I recovered the device. Is there another way I'm supposed to do this>
> 2) The other thing you can try is go to about:crashes, and see if there are GPU process crashes there. If yes, please share the crash hash with us and we could take a look.
I can't get Chrome to start up at all, so I can't go to about:crashes.
> 3) You can also run with --disable-gpu-sandbox and see if that fixes the problem. If yes, then we know it's some sandbox issue that prevents GPU process from launching.
Didn't get to this because of the note to #1.
Another note: I flashed to an older CrOS version from a few days back then flashed ToT Chrome and got this same issue. It does appear to be a regression in Chrome, not Chrome OS. I synced to ToT yesterday and was successfully able to deploy Chrome to my device via the Simple Chrome flow. With today's ToT, I run into this
kh...@chromium.org
Changing type to Bug-Regression since I've confirmed this is caused by a regression in Chrome from the past day. This is blocking my team from working on ToT - is P0 appropriate here?
zm...@google.com
I think the best path to resolve this is for someone who can reproduce the issue to bisect and revert the culprit CL.
kh...@chromium.org
Azeem is going to bisect this issue.
zm...@google.com
From the log messages, it looks like we fail to initialize GL because we fail to load the driver. Is there a sandbox change yesterday?
kh...@chromium.org
Adding RBD since Chrome cannot start up at all due to this issue. dgagnon@ FYI.
so...@google.com
In case it's related to glibc update
ma...@chromium.org
[Comment Deleted]
ll...@google.com
khorimoto@ can you try 3) from https://crbug.com/chromium/1199431#c5 only (without 1) or 2)) .
Would be good to know if this is a sandbox issue.
and can you attach /var/log/messages in here. We would like to see if there are any new seccomp issues.
and /var/log/audit/audit.log
I does not seem like glibc related because you reproduced the problem in an older chromeos image.
Would be good to know if this is a sandbox issue.
and can you attach /var/log/messages in here. We would like to see if there are any new seccomp issues.
and /var/log/audit/audit.log
I does not seem like glibc related because you reproduced the problem in an older chromeos image.
ma...@chromium.org
what is the first chrome os version that has this issue? fir chrome os image with newer glibc was 13915.0.0
kh...@chromium.org
> khorimoto@ can you try 3) from https://crbug.com/chromium/1199431#c5 only (without 1) or 2)) .
azeemarshad@ is looking into this.
> what is the first chrome os version that has this issue? fir chrome os image with newer glibc was 13915.0.0
I don't believe there is yet a Chrome OS build that has the issue. I can confirm that 13916.0.0 does *not* have the issue, but I haven't tried out 13917.0.0 (just built today) yet. This is a regression in Chrome during the past ~24 hours that I have been able to reproduce on both 13906.0.0 and 13916.0.0 via the Simple Chrome flow.
azeemarshad@ is looking into this.
> what is the first chrome os version that has this issue? fir chrome os image with newer glibc was 13915.0.0
I don't believe there is yet a Chrome OS build that has the issue. I can confirm that 13916.0.0 does *not* have the issue, but I haven't tried out 13917.0.0 (just built today) yet. This is a regression in Chrome during the past ~24 hours that I have been able to reproduce on both 13906.0.0 and 13916.0.0 via the Simple Chrome flow.
ma...@chromium.org
Oh I see, if it repros on 13906.0.0 then it is unrelated to glibc . I can sleep in peace for tonight :).
kh...@chromium.org
kh...@chromium.org
[Empty comment from Monorail migration]
kb...@chromium.org
[Empty comment from Monorail migration]
kh...@chromium.org
kh...@chromium.org
We haven't been able to figure out how to get this reverted with the new system that replaced TBR with OO. Reassigning to dstaessens@ who will get this completed since it is getting late where I am in California.
kh...@chromium.org
[Empty comment from Monorail migration]
gi...@appspot.gserviceaccount.com
The following revision refers to this bug:
https://chromium.googlesource.com/chromium/src/+/ff277a52ece0b216617d770f201ed66955fe70b9
commit ff277a52ece0b216617d770f201ed66955fe70b9
Author: Kyle Horimoto <khorimoto@chromium.org>
Date: Fri Apr 16 03:05:40 2021
Revert "Reland "Linux sandbox syscall broker: use struct kernel_stat""
This reverts commit cffbc4432af79f720ae3c75dff380b853701bd64.
Reason for revert:https://bugs.chromium.org/p/chromium/issues/detail?id=1199431
Original change's description:
commit ff277a52ece0b216617d770f201ed66955fe70b9
Author: Kyle Horimoto <khorimoto@chromium.org>
Date: Fri Apr 16 03:05:40 2021
Revert "Reland "Linux sandbox syscall broker: use struct kernel_stat""
This reverts commit cffbc4432af79f720ae3c75dff380b853701bd64.
Reason for revert:
Original change's description:
Fixed: 1199431
Change-Id: Iebfc0c48201bf22ff9c54d8d5c8a43d26a880098
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on:
Auto-Submit: Kyle Horimoto <khorimoto@chromium.org>
Commit-Queue: Matthew Denton <mpdenton@chromium.org>
Commit-Queue: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Matthew Denton <mpdenton@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Owners-Override: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#873173}
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[delete]
[modify]
ma...@chromium.org
[Empty comment from Monorail migration]
ll...@google.com
kb...@chromium.org
Does this bug refer to any unreleased product names?
kh...@chromium.org
> Does this bug refer to any unreleased product names?
Yes, the trogdor device. That being said, there have been mentions of this in the media; for example:https://chromeunboxed.com/qualcomm-snapdragon-chromebook-trogdor-clamshell/
Yes, the trogdor device. That being said, there have been mentions of this in the media; for example:
kb...@chromium.org
That news piece appears to have gone offline.
Folks on the ChromeOS side should decide - if you all think it's OK, feel free to remove the R-V-G label.
Folks on the ChromeOS side should decide - if you all think it's OK, feel free to remove the R-V-G label.
so...@google.com
trogdor is released
kb...@chromium.org
Thanks for the information. Unrestricting view.
gi...@appspot.gserviceaccount.com
The following revision refers to this bug:
https://chromium.googlesource.com/chromium/src/+/4b438323d68840453b5ef826c3997568e2e0e8c7
commit 4b438323d68840453b5ef826c3997568e2e0e8c7
Author: Matthew Denton <mpdenton@chromium.org>
Date: Mon Jul 19 14:03:13 2021
Reland "Reland "Linux sandbox syscall broker: use struct kernel_stat""
This reverts commit ff277a52ece0b216617d770f201ed66955fe70b9.
Reason for revert: reland
The fix included in the reland is that fstatat64() needs to be
allowed in the broker process's seccomp policy.
This CL also includes some extra tests that the kernel_stat structures
match the layout the kernel expects.
Bug: 1164975, 1199431
Test: trogdor Chromebook successfully boots and allows login.
Original change's description:
commit 4b438323d68840453b5ef826c3997568e2e0e8c7
Author: Matthew Denton <mpdenton@chromium.org>
Date: Mon Jul 19 14:03:13 2021
Reland "Reland "Linux sandbox syscall broker: use struct kernel_stat""
This reverts commit ff277a52ece0b216617d770f201ed66955fe70b9.
Reason for revert: reland
The fix included in the reland is that fstatat64() needs to be
allowed in the broker process's seccomp policy.
This CL also includes some extra tests that the kernel_stat structures
match the layout the kernel expects.
Bug: 1164975, 1199431
Test: trogdor Chromebook successfully boots and allows login.
Original change's description:
Change-Id: Ibe6a485070f33489aaa157b51b908c2d23d174d7
Reviewed-on:
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Matthew Denton <mpdenton@chromium.org>
Cr-Commit-Position: refs/heads/master@{#902981}
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[modify]
[add]
[modify]
[modify]
[modify]
[modify]
sa...@google.com
[Empty comment from Monorail migration]
is...@google.com
This issue was migrated from crbug.com/chromium/1199431?no_tracker_redirect=1
[Auto-CCs applied]
[Monorail blocked-on:crbug.com/chromium/1198480 ]
[Monorail blocking:crbug.com/chromium/1164975 ]
[Monorail components added to Component Tags custom field.]
[Auto-CCs applied]
[Monorail blocked-on:
[Monorail blocking:
[Monorail components added to Component Tags custom field.]
Description
CrOS Version: 13916.0.0
Chrome version: ToT, synced to 8bcb389de167c1dacddf49b832b5f9b30bffee2d
Upon starting Chrome, I get this crash:
2021-04-15T18:36:28.249792Z FATAL chrome[18173:18202]: [gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
#0 0x00000a002142 base::debug::CollectStackTrace()
#1 0x00000adec5b2 base::debug::StackTrace::StackTrace()
#2 0x00000acc501c logging::LogMessage::~LogMessage()
#3 0x000008b266e8 content::(anonymous namespace)::IntentionallyCrashBrowserForUnusableGpuProcess()
#4 0x000008b25018 content::GpuDataManagerImplPrivate::FallBackToNextGpuMode()
#5 0x000008b24354 content::GpuDataManagerImpl::FallBackToNextGpuMode()
#6 0x00000874a0ae viz::mojom::GpuHostStubDispatch::Accept()
#7 0x00000ad14364 mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept()
#8 0x00000ad27b8c mojo::MessageDispatcher::Accept()
#9 0x00000af57bd4 mojo::internal::MultiplexRouter::Accept()
#10 0x00000ad27b8c mojo::MessageDispatcher::Accept()
#11 0x00000ace1a64 mojo::Connector::ReadAllAvailableMessages()
#12 0x00000ac948e4 mojo::SimpleWatcher::OnHandleReady()
#13 0x00000ac945a2 mojo::SimpleWatcher::Context::CallNotify()
#14 0x000008961590 mojo::core::WatcherDispatcher::InvokeWatchCallback()
#15 0x000008961400 mojo::core::Watch::InvokeCallback()
#16 0x00000acccd02 mojo::core::RequestContext::~RequestContext()
#17 0x00000895926a mojo::core::NodeChannel::OnChannelMessage()
#18 0x000008951310 mojo::core::Channel::TryDispatchMessage()
#19 0x000008951164 mojo::core::Channel::OnReadComplete()
#20 0x00000ac5479c mojo::core::ChannelPosix::OnFileCanReadWithoutBlocking()
#21 0x00000b339ece base::MessagePumpLibevent::OnLibeventNotification()
#22 0x00000b143110 event_base_loop
#23 0x00000b142e04 base::MessagePumpLibevent::Run()
#24 0x000009fe851a base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#25 0x000009fcf7c0 base::RunLoop::Run()
#26 0x000009ff4240 base::Thread::Run()
#27 0x000008a62a64 content::BrowserProcessSubThread::IOThreadRun()
#28 0x000009ff436e base::Thread::ThreadMain()
#29 0x00000a00b6f2 base::(anonymous namespace)::ThreadFunc()
Full logs:
2021-04-15T18:36:28.087677Z WARNING chrome[1:1]: [hugepage_text.cc(212)] Orderfile ordered fewer than 8 huge pages.
2021-04-15T18:36:28.087693Z WARNING chrome[18181:18181]: [hugepage_text.cc(212)] Orderfile ordered fewer than 8 huge pages.
2021-04-15T18:36:28.175945Z ERROR chrome[18173:18173]: [kstaled.cc(57)] Unable to configure kstaled: no kernel support
2021-04-15T18:36:28.189355Z VERBOSE1 chrome[18173:18173]: [drm_display_host_manager.cc(123)] Failed to get DRM resources for '/dev/dri/card0': Operation not supported (95)
2021-04-15T18:36:28.189547Z VERBOSE1 chrome[18173:18173]: [drm_device_handle.cc(95)] Succeeded authenticating /dev/dri/card1 in 0 ms with 1 attempt(s)
2021-04-15T18:36:28.199350Z WARNING chrome[18173:18224]: [camera_hal_dispatcher_impl.cc(437)] Building Mojo channel. Socket info: creation_time: 2021-04-15 18:36:28.198 UTC last_accessed: 2021-04-15 18:36:28.198 UTC last_modified: 2021-04-15 18:36:28.198 UTC
2021-04-15T18:36:28.227801Z ERROR chrome[18237:18237]: [gl_surface_egl.cc(780)] EGL Driver message (Error) eglInitialize: DRI2: failed to load driver
2021-04-15T18:36:28.228753Z ERROR chrome[18237:18237]: [gl_surface_egl.cc(780)] EGL Driver message (Error) eglInitialize: DRI2: failed to load driver
2021-04-15T18:36:28.228825Z ERROR chrome[18237:18237]: [gl_surface_egl.cc(780)] EGL Driver message (Error) eglInitialize: eglInitialize
2021-04-15T18:36:28.228881Z ERROR chrome[18237:18237]: [gl_surface_egl.cc(1373)] eglInitialize Default failed with error EGL_NOT_INITIALIZED
2021-04-15T18:36:28.228933Z ERROR chrome[18237:18237]: [gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
2021-04-15T18:36:28.249014Z ERROR chrome[18237:18237]: [viz_main_impl.cc(160)] Exiting GPU process due to errors during initialization
2021-04-15T18:36:28.255779Z WARNING chrome[18173:18203]: [name_value_pairs_parser.cc(131)] Statistics wpsw_cur mentioned in /usr/bin/crossystem: 777073775F637572202020202020202020202020202020203D203020202020202020202020202020202020202020202020202020202020202023205B524F2F696E745D204669726D776172652077726974652070726F74656374206861726477617265207377697463682063757272656E7420706F736974696F6E
2021-04-15T18:36:28.256819Z WARNING chrome[18173:18203]: [name_value_pairs_parser.cc(131)] Statistics wpsw_cur mentioned in /tmp/machine-info: 777073775F6375723D223122
2021-04-15T18:36:28.269593Z WARNING chrome[18173:18203]: [statistics_provider.cc(320)] Finished loading statistics.
2021-04-15T18:36:28.342265Z VERBOSE1 chrome[18173:18173]: [arc_session_manager.cc(1603)] Started expanding *.prop files
2021-04-15T18:36:28.342334Z VERBOSE1 chrome[18173:18173]: [arc_util.cc(424)] Starting arc-prepare-host-generated-dir
2021-04-15T18:36:28.363217Z WARNING chrome[18173:18173]: [nearby_sharing_service_factory.cc(91)] BuildServiceInstanceFor: Nearby Share not supported for browser context.
2021-04-15T18:36:28.380928Z ERROR chrome[18173:18173]: [input_method_manager_impl.cc(1111)] IMEEngine for "fgoepimhcoialccpbmpnnblemnepkkao" is not registered
2021-04-15T18:36:28.386509Z WARNING chrome[18173:18173]: [browser_manager.cc(691)] Session not yet active. Lacros-chrome will not be launched yet
2021-04-15T18:36:28.249792Z FATAL chrome[18173:18202]: [gpu_data_manager_impl_private.cc(415)] GPU process isn't usable. Goodbye.
#0 0x00000a002142 base::debug::CollectStackTrace()
#1 0x00000adec5b2 base::debug::StackTrace::StackTrace()
#2 0x00000acc501c logging::LogMessage::~LogMessage()
#3 0x000008b266e8 content::(anonymous namespace)::IntentionallyCrashBrowserForUnusableGpuProcess()
#4 0x000008b25018 content::GpuDataManagerImplPrivate::FallBackToNextGpuMode()
#5 0x000008b24354 content::GpuDataManagerImpl::FallBackToNextGpuMode()
#6 0x00000874a0ae viz::mojom::GpuHostStubDispatch::Accept()
#7 0x00000ad14364 mojo::InterfaceEndpointClient::HandleIncomingMessageThunk::Accept()
#8 0x00000ad27b8c mojo::MessageDispatcher::Accept()
#9 0x00000af57bd4 mojo::internal::MultiplexRouter::Accept()
#10 0x00000ad27b8c mojo::MessageDispatcher::Accept()
#11 0x00000ace1a64 mojo::Connector::ReadAllAvailableMessages()
#12 0x00000ac948e4 mojo::SimpleWatcher::OnHandleReady()
#13 0x00000ac945a2 mojo::SimpleWatcher::Context::CallNotify()
#14 0x000008961590 mojo::core::WatcherDispatcher::InvokeWatchCallback()
#15 0x000008961400 mojo::core::Watch::InvokeCallback()
#16 0x00000acccd02 mojo::core::RequestContext::~RequestContext()
#17 0x00000895926a mojo::core::NodeChannel::OnChannelMessage()
#18 0x000008951310 mojo::core::Channel::TryDispatchMessage()
#19 0x000008951164 mojo::core::Channel::OnReadComplete()
#20 0x00000ac5479c mojo::core::ChannelPosix::OnFileCanReadWithoutBlocking()
#21 0x00000b339ece base::MessagePumpLibevent::OnLibeventNotification()
#22 0x00000b143110 event_base_loop
#23 0x00000b142e04 base::MessagePumpLibevent::Run()
#24 0x000009fe851a base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#25 0x000009fcf7c0 base::RunLoop::Run()
#26 0x000009ff4240 base::Thread::Run()
#27 0x000008a62a64 content::BrowserProcessSubThread::IOThreadRun()
#28 0x000009ff436e base::Thread::ThreadMain()
#29 0x00000a00b6f2 base::(anonymous namespace)::ThreadFunc()
2021-04-15T18:36:28.611428Z ERROR crashpad_handler: [elf_dynamic_array_reader.h(61)] tag not found
2021-04-15T18:36:28.644917Z INFO crashpad_handler: [cros_crash_report_exception_handler.cc(283)] Successfully wrote report 4a0931da-3cf5-4e68-9ea0-fa6e42a8380f
2021-04-15T18:36:28.730490Z ERROR chrome[18304:1]: [broker_posix.cc(43)] Invalid node channel message
2021-04-15T18:36:28.730595Z ERROR chrome[18298:1]: [broker_posix.cc(43)] Invalid node channel message
2021-04-15T18:36:28.730605Z ERROR chrome[18299:1]: [broker_posix.cc(43)] Invalid node channel message
2021-04-15T18:36:28.924570Z WARNING chrome[18326:18326]: [hugepage_text.cc(212)] Orderfile ordered fewer than 8 huge pages.
2021-04-15T18:36:28.945531Z WARNING chrome[1:1]: [hugepage_text.cc(212)] Orderfile ordered fewer than 8 huge pages.
2021-04-15T18:36:29.021511Z ERROR chrome[18318:18318]: [kstaled.cc(57)] Unable to configure kstaled: no kernel support
2021-04-15T18:36:29.046609Z VERBOSE1 chrome[18318:18318]: [drm_display_host_manager.cc(123)] Failed to get DRM resources for '/dev/dri/card0': Operation not supported (95)
2021-04-15T18:36:29.047165Z VERBOSE1 chrome[18318:18318]: [drm_device_handle.cc(95)] Succeeded authenticating /dev/dri/card1 in 0 ms with 1 attempt(s)
2021-04-15T18:36:29.058608Z WARNING chrome[18318:18363]: [camera_hal_dispatcher_impl.cc(437)] Building Mojo channel. Socket info: creation_time: 2021-04-15 18:36:29.056 UTC last_accessed: 2021-04-15 18:36:29.056 UTC last_modified: 2021-04-15 18:36:29.056 UTC
2021-04-15T18:36:29.088096Z ERROR chrome[18375:18375]: [gl_surface_egl.cc(780)] EGL Driver message (Error) eglInitialize: DRI2: failed to load driver
2021-04-15T18:36:29.089063Z ERROR chrome[18375:18375]: [gl_surface_egl.cc(780)] EGL Driver message (Error) eglInitialize: DRI2: failed to load driver
2021-04-15T18:36:29.089153Z ERROR chrome[18375:18375]: [gl_surface_egl.cc(780)] EGL Driver message (Error) eglInitialize: eglInitialize
2021-04-15T18:36:29.089223Z ERROR chrome[18375:18375]: [gl_surface_egl.cc(1373)] eglInitialize Default failed with error EGL_NOT_INITIALIZED
2021-04-15T18:36:29.089291Z ERROR chrome[18375:18375]: [gl_ozone_egl.cc(20)] GLSurfaceEGL::InitializeOneOff failed.
2021-04-15T18:36:29.100665Z WARNING chrome[18318:18339]: [name_value_pairs_parser.cc(131)] Statistics wpsw_cur mentioned in /usr/bin/crossystem: 777073775F637572202020202020202020202020202020203D203020202020202020202020202020202020202020202020202020202020202023205B524F2F696E745D204669726D776172652077726974652070726F74656374206861726477617265207377697463682063757272656E7420706F736974696F6E
2021-04-15T18:36:29.101453Z WARNING chrome[18318:18339]: [name_value_pairs_parser.cc(131)] Statistics wpsw_cur mentioned in /tmp/machine-info: 777073775F6375723D223122
2021-04-15T18:36:29.108769Z ERROR chrome[18375:18375]: [viz_main_impl.cc(160)] Exiting GPU process due to errors during initialization
2021-04-15T18:36:29.113778Z WARNING chrome[18318:18339]: [statistics_provider.cc(320)] Finished loading statistics.
2021-04-15T18:36:29.171481Z VERBOSE1 chrome[18318:18318]: [arc_session_manager.cc(1603)] Started expanding *.prop files
2021-04-15T18:36:29.171560Z VERBOSE1 chrome[18318:18318]: [arc_util.cc(424)] Starting arc-prepare-host-generated-dir
2021-04-15T18:36:29.189962Z WARNING chrome[18318:18318]: [nearby_sharing_service_factory.cc(91)] BuildServiceInstanceFor: Nearby Share not supported for browser context.
2021-04-15T18:36:29.206525Z ERROR chrome[18318:18318]: [input_method_manager_impl.cc(1111)] IMEEngine for "fgoepimhcoialccpbmpnnblemnepkkao" is not registered
2021-04-15T18:36:29.212201Z WARNING chrome[18318:18318]: [browser_manager.cc(691)] Session not yet active. Lacros-chrome will not be launched yet
CC'ing gardeners and GpuDataManagerImpl owners.