Chrome crashes during continuous meeting test |
||||
Issue description
Guado in meeting mode running:
chromeOS: 9765.85.0 Chrome: 61.0.3163.123
What steps will reproduce the problem?
(1) Having device joining/leaving meeting
What is the expected result?
No crash
What happens instead?
chrome crashed
Please use labels and text to provide additional information.
================================================================
localhost crash # ls -altr
total 576192
drwxr-xr-x 5 root root 4096 Oct 11 14:12 ..
-rw-r--r-- 1 root root 25095 Oct 17 13:27 chrome.20171017.132747.3740.log
-rw-r--r-- 1 root root 76619776 Oct 17 13:27 chrome.20171017.132747.3740.core
-rw------- 1 root root 115816 Oct 17 13:27 chrome.20171017.132747.3740.dmp
-rw-r--r-- 1 root root 168 Oct 17 13:27 chrome.20171017.132747.3740.meta
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132806.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132813.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132820.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132826.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132833.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132840.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132847.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:28 change_card0_drm.20171017.132854.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132900.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132906.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132912.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132918.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132924.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132931.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132937.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132944.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:29 change_card0_drm.20171017.132951.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.132959.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133005.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133012.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133018.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133024.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133030.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133036.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133043.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133049.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:30 change_card0_drm.20171017.133056.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:31 change_card0_drm.20171017.133103.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:31 change_card0_drm.20171017.133110.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:31 change_card0_drm.20171017.133117.0.log
-rw-r--r-- 1 root root 16553512 Oct 17 13:31 change_card0_drm.20171017.133124.0.log
drwxr-xr-t 2 root root 4096 Oct 17 14:24 .
localhost crash # cd /var/log/chrome/
localhost chrome # ls -altr
total 45636
-rw-r--r-- 1 chronos chronos 2062851 Oct 17 13:37 chrome_20171017-131835
-rw-r--r-- 1 chronos chronos 178473 Oct 17 13:38 chrome_20171017-133710
-rw-r--r-- 1 chronos chronos 16659 Oct 17 13:40 chrome_20171017-133857
-rw-r--r-- 1 chronos chronos 2724024 Oct 17 14:05 chrome_20171017-134017
-rw-r--r-- 1 chronos chronos 452043 Oct 17 14:10 chrome_20171017-140551
-rw-r--r-- 1 chronos chronos 104704 Oct 17 14:11 chrome_20171017-141031
-rw-r--r-- 1 chronos chronos 20761 Oct 17 14:12 chrome_20171017-141131
-rw-r--r-- 1 chronos chronos 18944 Oct 17 14:12 chrome_20171017-141211
-rw-r--r-- 1 chronos chronos 1250162 Oct 17 14:20 chrome_20171017-141301
drwx------ 2 chronos chronos 4096 Oct 17 14:20 'Crash Reports'
lrwxrwxrwx 1 chronos chronos 38 Oct 17 14:20 chrome -> /var/log/chrome/chrome_20171017-142052
drwxrwxr-t 11 root syslog 4096 Oct 17 14:28 ..
drwxr-xr-x 3 chronos chronos 12288 Oct 17 14:29 .
-rw-r--r-- 1 chronos chronos 1988134 Oct 17 14:32 chrome_20171017-142052
localhost chrome # cat /etc/lsb-release
CHROMEOS_RELEASE_APPID={8AA6D9AC-6EBC-4288-A615-171F56F66B4E}
CHROMEOS_BOARD_APPID={8AA6D9AC-6EBC-4288-A615-171F56F66B4E}
CHROMEOS_CANARY_APPID={90F229CE-83E2-4FAF-8479-E368A34938B1}
DEVICETYPE=CHROMEBOX
CHROMEOS_RELEASE_BUILDER_PATH=guado-release/R61-9765.85.0
GOOGLE_RELEASE=9765.85.0
CHROMEOS_DEVSERVER=
CHROMEOS_RELEASE_BOARD=guado
CHROMEOS_RELEASE_BUILD_NUMBER=9765
CHROMEOS_RELEASE_BRANCH_NUMBER=85
CHROMEOS_RELEASE_CHROME_MILESTONE=61
CHROMEOS_RELEASE_PATCH_NUMBER=0
CHROMEOS_RELEASE_TRACK=testimage-channel
CHROMEOS_RELEASE_DESCRIPTION=9765.85.0 (Official Build) dev-channel guado test
CHROMEOS_RELEASE_BUILD_TYPE=Official Build
CHROMEOS_RELEASE_NAME=Chrome OS
CHROMEOS_RELEASE_VERSION=9765.85.0
CHROMEOS_AUSERVER=https://tools.google.com/service/update2
localhost chrome # uptime
14:32:55 up 20:56, 0 users, load average: 2.22, 2.23, 2.35
localhost chrome # tail -20 /var/log/eventlog.txt
237 | 2017-10-16 14:40:54 | Kernel Event | Clean Shutdown
238 | 2017-10-16 14:40:54 | System boot | 656
239 | 2017-10-16 14:40:54 | System Reset
240 | 2017-10-16 14:40:54 | Wake Source | GPIO | 27
241 | 2017-10-16 14:40:55 | Chrome OS Developer Mode
242 | 2017-10-16 15:22:55 | Kernel Event | Clean Shutdown
243 | 2017-10-16 15:22:56 | System boot | 657
244 | 2017-10-16 15:22:56 | System Reset
245 | 2017-10-16 15:22:56 | Wake Source | GPIO | 27
246 | 2017-10-16 15:22:57 | Chrome OS Developer Mode
247 | 2017-10-16 17:13:14 | Kernel Event | Clean Shutdown
248 | 2017-10-16 17:13:15 | System boot | 658
249 | 2017-10-16 17:13:15 | System Reset
250 | 2017-10-16 17:13:15 | Wake Source | GPIO | 27
251 | 2017-10-16 17:13:15 | Chrome OS Developer Mode
252 | 2017-10-16 17:35:44 | Kernel Event | Clean Shutdown
253 | 2017-10-16 17:35:45 | System boot | 659
254 | 2017-10-16 17:35:45 | System Reset
255 | 2017-10-16 17:35:45 | Wake Source | GPIO | 27
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
,
Oct 17 2017
Log files, crash files and debug log file are uploaded to https://drive.google.com/corp/drive/u/0/folders/1ydSIrHsAqfMAji0TVzAHnQ9A9l3cTEiw.
,
Oct 19 2017
Definitely not infra, speculating graphics, but you may want a project specific component...
,
Oct 25 2017
,
Oct 25 2017
Duplicate of crbug.com/663490, which is marked as WontFix at the moment. I agree with comment#3 that this is gpu related. But this is not really a bug, as much as it is an extreme corner case with the gpu taking a little longer than it should drawing a frame and the watchdog thinking there is a timeout. This is the link to the identical crash report: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_ChromeOS%27%20AND%20crash.Address%3D0%20AND%20custom_data.ChromeCrashProto.ptype%3D%27gpu-process%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=d7587cb800156ea7&index=34#0. I am also attaching the stackwalk I gathered from comment#2 on this thread, which shows the almost identical stacktrace at the moment of crash. There is not much to do at this point but keep an eye out to see how often we see this. But it seems like it's really rare. The crash report I linked to refers to this segfault as "longstanding unavoidable crash."
,
Oct 25 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by jbudorick@chromium.org
, Oct 17 2017