Chrome OS browser exits with illegal instruction?

Xiaoyong Zhou

unread,

Aug 9, 2019, 4:54:57 PM8/9/19

to Chromium OS Development

I build chrome for chrome os using the simple instruction and each time I flash a fresh build chrome to chrome os devices, the browser keep crashing, with the following errors:

2019-08-09T13:46:59.873028-07:00 CRIT kernel: [ 26.887066] CPU0: Package temperature above threshold, cpu clock throttled (total events = 1)

2019-08-09T13:46:59.875010-07:00 INFO kernel: [ 26.889019] CPU0: Core temperature/speed normal

2019-08-09T13:46:59.875015-07:00 INFO kernel: [ 26.889020] CPU2: Package temperature/speed normal

2019-08-09T13:46:59.875017-07:00 INFO kernel: [ 26.889024] CPU0: Package temperature/speed normal

2019-08-09T13:47:00.869113-07:00 ERR chapsd[1104]: Concurrent sessions

2019-08-09T13:47:00.876888-07:00 INFO metrics_daemon[2950]: [INFO:metrics_daemon.cc(513)] Got org.chromium.PowerManager.PowerSupplyPoll D-Bus signal

2019-08-09T13:47:04.891499-07:00 INFO metrics_daemon[2950]: message repeated 4 times: [ [INFO:metrics_daemon.cc(513)] Got org.chromium.PowerManager.PowerSupplyPoll D-Bus signal]

2019-08-09T13:47:15.845877-07:00 INFO sshd[3610]: Accepted publickey for root from 127.0.0.1 port 40068 ssh2: RSA SHA256:Fp1qWjFLyK1cTpiI5rdk7iEJwoK9lcnYAgbQtGC3jzU

2019-08-09T13:47:22.220534-07:00 WARNING mosys[3728]: libminijail[3728]: not locking any securebits

2019-08-09T13:47:22.220628-07:00 WARNING mosys[3728]: libminijail[3728]: SECURE_NOROOT not set, not dropping bounding set

2019-08-09T13:47:34.897222-07:00 INFO metrics_daemon[2950]: [INFO:metrics_daemon.cc(513)] Got org.chromium.PowerManager.PowerSupplyPoll D-Bus signal

2019-08-09T13:47:36.655523-07:00 WARNING crash_reporter[3863]: Received crash notification for chrome[1668] user 1000 (called directly)

2019-08-09T13:47:36.657037-07:00 INFO crash_reporter[3863]: Accessing crash dir '/home/user/73a027d225ca0bed63156464486c4915ccdb8f0c/crash' via symlinked handle '/proc/self/fd/11'

2019-08-09T13:47:37.135190-07:00 WARNING crash_reporter[3881]: Received crash notification for chrome[1668] user 1000 (called directly)

2019-08-09T13:47:37.136368-07:00 INFO crash_reporter[3881]: Accessing crash dir '/home/user/73a027d225ca0bed63156464486c4915ccdb8f0c/crash' via symlinked handle '/proc/self/fd/11'

2019-08-09T13:47:37.493055-07:00 INFO kernel: [ 64.488699] traps: chrome[1668] trap invalid opcode ip:575ff2e49442 sp:7ffe9dd09770 error:0 in chrome[575feeb66000+a568000]

2019-08-09T13:47:37.517131-07:00 WARNING crash_reporter[3897]: [user] Received crash notification for chrome[1668] sig 4, user 1000 group 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)

2019-08-09T13:47:37.540612-07:00 ERR cros_camera_service[2152]: OnDispatcherError(): Mojo channel to CameraHalDispatcher is broken

2019-08-09T13:47:37.540688-07:00 INFO cros_camera_service[2152]: OnServiceMojoChannelError(): Mojo connection to CameraHalDispatcher is broken

2019-08-09T13:47:37.551571-07:00 INFO cros_camera_service[2123]: main(): Child exited: status=104

2019-08-09T13:47:37.608764-07:00 INFO session_manager[1646]: [INFO:session_manager_service.cc(289)] Browser process 1668 exited with signal 4 (Illegal instruction)

2019-08-09T13:47:37.608827-07:00 INFO session_manager[1646]: [INFO:browser_job.cc(188)] Terminating process group for browser 1668 with signal 9: Ensuring browser processes are gone.

2019-08-09T13:47:37.608872-07:00 INFO session_manager[1646]: [INFO:system_utils_impl.cc(128)] Sending signal 9 to PID -1668 as UID 1000

2019-08-09T13:47:37.609859-07:00 INFO session_manager[1646]: [INFO:browser_job.cc(208)] Waiting up to 3 seconds for 1668's process group to exit

2019-08-09T13:47:38.331476-07:00 INFO session_manager[1646]: [INFO:browser_job.cc(218)] Cleaned up browser process 1668

2019-08-09T13:47:38.334104-07:00 INFO session_manager[1646]: [INFO:browser_job.cc(175)] Running browser /opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=32.0.0.238 --use-gl=egl --enable-native-gpu-memory-buffers --enable-webgl-image-chromium --enable-features=Pepper3DImageChromium,PointerEvent,MachineLearningService,ChromeOSAssistant,EnableBackgroundBlur,MyFilesVolume,Crostini,ExperimentalCrostiniUI,CrostiniGpuSupport --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --system-developer-mode --disable-logging-redirect --login-profile=user --has-chromeos-keyboard --enable-touchview --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --child-wallpaper-large=/usr/share/chromeos-assets/wallpaper/child_large.jpg --child-wallpaper-small=/usr/share/chromeos-assets/wallpaper/child_small.jpg --default-wallpaper-large=/usr/share/chromeos-assets/wallpaper/oem_large.jpg --default-wallpaper-small=/usr/share/chromeos-assets/wallpaper/oem_small.jpg --default-wallpaper-is-oem --arc-availability=officially-supported --enable-arc-oobe-optin --enable-arc-oobe-optin-no-skip --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --login-user=cdev...@gmail.com --login-profile=73a027d225ca0bed63156464486c4915ccdb8f0c --vmodule=*/chrome/browser/chromeos/account_manager/*=1,*/chromeos/components/account_manager/*=1,*arc/*=1,app_list_syncable_service=1,*/chromeos/power/auto_screen_brightness/*=1,*/forced_extensions/installation_tracker*=2,extension_downloader=2,existing_user_controller=2,*/ash/wm/tablet_mode/*=1,auto_enrollment_controller=1,*/ui/ozone/*=1,*/ui/display/manager/chromeos/*=1,update_engine=1,component_updater_service=1 --enable-features=Pepper3DImageChromium,PointerEvent,MachineLearningService,ChromeOSAssistant,EnableBackgroundBlur,MyFilesVolume,Crostini,ExperimentalCrostiniUI,CrostiniGpuSupport

2019-08-09T13:47:38.338576-07:00 INFO session_manager[1646]: [INFO:session_manager_service.cc(236)] Browser is 3913

2019-08-09T13:47:38.600897-07:00 NOTICE temp_logger[3955]: 00:57 02:40 03:38 04:44 05:47 06:57 07:42

Is there a build breakage?

Jinyoung Hur

unread,

Jul 30, 2020, 3:25:12 AM7/30/20

to Chromium OS Development

Hi,

I guess I got the same problem.

Could you give me a tip if you have addressed this problem?

Allen Webb

unread,

Jul 30, 2020, 10:16:29 AM7/30/20

to Jinyoung Hur, Chromium OS Development

Make sure you are building Chrome with the same SDK you are using for chrome os.

One thing that helps is pointing the chrome build process to the chroot you are using here is an example:

export BOARD=sand
cros chrome-sdk --internal --chroot /usr/local/google/home/allenwebb/NoBackup/chromeos2/chroot --board=$BOARD --log-level=info

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev
---
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

Kevin Chowski

unread,

Jul 30, 2020, 10:41:52 AM7/30/20

to Allen Webb, Jinyoung Hur, Chromium OS Development

Jinyoung Hur, some clarifying questions:

* what board are you trying to use?

* what commands are you using to build? (all commands you are executing, starting at a standard terminal)

* do you have any local changes to the source?

Reply all

Reply to author

Forward