New issue
Advanced search Search tips

Issue 681685 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Nov 8
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Chromebook freezing

Reported by jfleming...@gmail.com, Jan 16 2017

Issue description


Google Inc.
Copyright 2017 Google Inc. All rights reserved.
Google Chrome	56.0.2924.58 (Official Build) beta (32-bit)
Revision	0
Platform	9000.58.0 (Official Build) beta-channel nyan_big
JavaScript	V8 5.6.326.33
Flash	24.0.0.194 /opt/google/chrome/pepper/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; CrOS armv7l 9000.58.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.58 Safari/537.36
Command Line	/opt/google/chrome/chrome --ppapi-flash-path=/opt/google/chrome/pepper/libpepflashplayer.so --ppapi-flash-version=24.0.0.194 --ppapi-flash-args=enable_hw_video_decode=0,enable_hw_video_decode_ave=0 --ui-prioritize-in-gpu-process --use-gl=egl --gpu-sandbox-failures-fatal=yes --enable-logging --log-level=1 --use-cras --enable-wayland-server --user-data-dir=/home/chronos --max-unused-resource-memory-usage-percentage=5 --login-profile=user --has-chromeos-keyboard --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 --guest-wallpaper-large=/usr/share/chromeos-assets/wallpaper/guest_large.jpg --guest-wallpaper-small=/usr/share/chromeos-assets/wallpaper/guest_small.jpg --enable-prefixed-encrypted-media --enable-consumer-kiosk --enterprise-enrollment-initial-modulus=15 --enterprise-enrollment-modulus-limit=19 --vmodule=screen_locker=2,webui_screen_locker=2,lock_state_controller=2,webui_login_view=2,power_button_observer=2,*ui/display/chromeos*=1,*ash/display*=1,*ui/ozone*=1,*zygote*=1,*plugin*=2,auto_enrollment_controller=1,*chromeos/login/*=1 --login-manager --first-exec-after-boot
Executable Path	/opt/google/chrome/chrome
Profile Path	/home/chronos/u-f18d6964ed416701f0a4b6fbb45382cf860edd09
Variations	6a89113b-a7aa8ed
68ebfce2-babc1d7f
90757ebb-3f4a17df
1e528f0f-ca7d8d80
6345b824-3d47f4f4
38eb801c-3f4a17df
8364a5c2-a684e2b8
7c1bc906-8122a015
2a33b90e-eb524a27
ba3f87da-a6404135
58aac55e-3f4a17df
31362330-ca7d8d80
811bc6bc-d93a0620
98be3390-d93a0620
9e201a2b-3f4a17df
5274eb09-3f4a17df
684d1cdf-f23d1dea
9e5c75f1-efb39c19
6b121ae7-ca7d8d80
f79cb77b-3f4a17df
b7786474-d93a0620
23a898eb-ca7d8d80
74df3f1-3f4a17df
4ea303a6-3f4a17df
9736de91-ca7d8d80
64005e71-80deee2a
3326cd71-3f4a17df
ca314179-ca7d8d80
69bf80fa-f23d1dea
b2f0086-93053e47
7fc902e8-3f4a17df
adda5502-ca7d8d80
3ac60855-486e2a9c
f296190c-610f13e6
4442aae2-6e597ede
ed1d377-e1cc0f14
75f0f0a0-a5822863
e2b18481-3a9ae350
e7e71889-4ad60575
828a5926-8f2c913

I have not yet been able to determine the triggering event.  It seems arbitrary where there can be minutes/hours between a freeze and reboot or days between.

 
debug-logs_20170116-150147.tgz
1.6 MB Download
net-internals-log.json
475 KB View Download

Comment 1 by ajha@chromium.org, Jan 17 2017

Labels: OS-Chrome
Log Analyzer found "NOTREACHED()" and "TPM error 0x21".
Does it ever crash after a freeze? Can you supply some crash ids from chrome://crashes 
I think that's how I'd (better) describe the issue.  I'll just be doing
whatever and the everything on the screen will freeze and the mouse will
stop responding.  If there is any audio then the last sound produced before
the freeze will continue being produced until the computer finally
reboots.  So maybe the best way to describe it would be a full system
freeze followed shortly be a reboot.  I've included crash IDs below (and
attached).
After following the Provide additional details link I decided not to create
a new issue but I thought I'd include the version from there:

Chrome Version: 56.0.2924.67Operating System: Linux 3.10.18

Crashes
Start uploading crashes
Crashes (3)
Crash ID Chrome (Server ID: a8f9a14680000000)

Automatically reported Wednesday, January 25, 2017 at 5:59:36 AM

Provide additional details
<https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2056.0.2924.67%0AOperating%20System%3A%20Linux%203.10.18%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2Fa8f9a14680000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted>
Crash ID Chrome (Server ID: 82429d8880000000)

Automatically reported Monday, January 23, 2017 at 9:08:50 PM

Provide additional details
<https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2056.0.2924.67%0AOperating%20System%3A%20Linux%203.10.18%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F82429d8880000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted>
Crash ID ChromeOS (Server ID: 82fde6e580000000)

Automatically reported Saturday, January 21, 2017 at 8:30:22 PM

Provide additional details
<https://code.google.com/p/chromium/issues/entry?template=Crash%20Report&comment=IMPORTANT%3A%20Your%20crash%20has%20already%20been%20automatically%20reported%20to%20our%20crash%20system.%20Please%20file%20this%20bug%20only%20if%20you%20can%20provide%20more%20information%20about%20it.%0A%0A%0AChrome%20Version%3A%2056.0.2924.67%0AOperating%20System%3A%20Linux%203.10.18%0A%0AURL%20(if%20applicable)%20where%20crash%20occurred%3A%0A%0ACan%20you%20reproduce%20this%20crash%3F%0A%0AWhat%20steps%20will%20reproduce%20this%20crash%3F%20(If%20it%27s%20not%20reproducible%2C%20what%20were%20you%20doing%20just%20before%20the%20crash%3F)%0A1.%0A2.%0A3.%0A%0A****DO%20NOT%20CHANGE%20BELOW%20THIS%20LINE****%0ACrash%20ID%3A%20crash%2F82fde6e580000000&labels=Restrict-View-EditIssue%2CStability-Crash%2CUser-Submitted>
There are just now two more.  Not sure what caused them, I don't recall
experiencing any issues at these times.

Crash ID Chrome (Server ID: e915821580000000)

Automatically reported Thursday, January 26, 2017 at 10:00:19 PM
Crash ID Chrome (Server ID: 2085821580000000)

Automatically reported Thursday, January 26, 2017 at 9:57:19 PM


Also I'm not completely sure there is a crash report for every instance of
the computer freezing and rebooting.  I only enabled crash reports somewhat
recently.
I wanted to add a couple things here.  I have a more recent debug log attached.  I also have a picture of the active chrome://net-internals/#events.  I had khan academy up at the time.  I don't know if the debug logs capture this data (and I haven't looked into it) and I thought it might be useful. Below are new Crash IDs, though there is probably one from January 28th (just a few minutes ago) that I don't have yet.

Crash ID Chrome (Server ID: 62a2d61580000000)

Automatically reported Friday, January 27, 2017 at 7:11:56 PM

Crash ID Chrome (Server ID: 725f43c880000000)

Automatically reported Friday, January 27, 2017 at 7:02:42 PM

IMG_20170127_180214.jpg
4.6 MB View Download
debug-logs_20170128-165059.tgz
1.8 MB Download
Components: OS>Kernel
From c#4 "So maybe the best way to describe it would be a full system
freeze followed shortly be a reboot." Looks like a kernel issue
I was running the beta channel at the time, I switched to the production
channel and the issue doesn't seem to present itself there.
Project Member

Comment 10 by sheriffbot@chromium.org, Nov 8

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

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

Sign in to add a comment