Chrome crash when running telemetry api to start meeting and get_device with PTZ camera connected |
|||||||||||
Issue description
Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)
Model ASUS Chromebox CN62
Serial Number H4MSCX002277
Google Chrome Version 61.0.3163.38
Platform Version 9765.21.0 (Official Build) dev-channel guado test
Firmware Version Google_Guado.6301.108.4
Boot Mode Dev
Enrollment Date Aug 15, 2017
Directory API ID abc4e8d0-347c-436c-94f8-f118b930358c
What steps will reproduce the problem?
(1)Run autotest to use telemetry to start meeting.
(2)Check whether page is in meeting.
(3)if yes, run telemetry to query device.
What is the expected result?
What happens instead?
in step 2 or 3 chrome crash.
Please use labels and text to provide additional information.
------------------------------------------------------------
Chrome crash happens each time running the script on setup which has PTZ camera.
Crash happens after joining meeting.
13:04:23 INFO | autoserv| XMLRPC server started successfully.
13:04:24 INFO | autoserv| wait for telemetry
13:04:32 INFO | autoserv| thor meeting joined
13:04:32 INFO | autoserv| wait for meeting in call page
13:04:32 INFO | autoserv| Failed RPC 'cfm.wait_for_meetings_in_call_page'((), {}) with status [<type 'exceptions.Exception'>].
13:04:32 INFO | autoserv| Exception : RPC error: cfm.wait_for_meetings_in_call_page
13:04:32 INFO | autoserv| Traceback (most recent call last):
13:04:32 INFO | autoserv| File "./multimedia_xmlrpc_server.py", line 89, in _dispatch
13:04:32 INFO | autoserv| return func(*params)
nterprise_CFM_CameraMuteStress/crashinfo.100.123.171.19/chrome.20170816.110443.6220.dmp
13:04:45 INFO | autoserv| INFO ---- Orphaned Crash Dump timestamp=1502906685 localtime=Aug 16 13:04:45 /var/spool/crash/chrome.20170816.110443.6220.core
13:04:45 INFO | autoserv| INFO ---- Orphaned Crash Dump timestamp=1502906685 localtime=Aug 16 13:04:45 /var/spool/crash/chrome.20170816.110443.6220.log
13:04:45 INFO | autoserv| INFO ---- Orphaned Crash Dump timestamp=1502906685 localtime=Aug 16 13:04:45 /var/spool/crash/chrome.20170816.110443.6220.meta
13:04:45 INFO | autoserv| INFO ---- Orphaned Crash Dump timestamp=1502906685 localtime=Aug 16 13:04:45 /var/spool/crash/chrome.20170816.110443.6220.dmp
13:04:45 INFO | autoserv| INFO ---- ---- timestamp=1502906685 localtime=Aug 16 13:04:45 End crashcollection record
13:04:45 INFO | autoserv| Crash detection failed with: [Errno 2] No such file or directory: '/var/spool/crash/chrome.20170816.110443.6220.meta'
13:04:45 INFO | autoserv| Crash detection failed with: [Errno 2] No such file or directory: '/var/spool/crash/chrome.20170816.110443.6220.meta'
13:04:45 INFO | autoserv| Crash detection failed with: [Errno 2] No such file or directory: '/var/spool/crash/chrome.20170816.110443.6220.meta'
13:04:45 INFO | autoserv| Crash detection failed with: [Errno 2] No such file or directory: '/var/spool/crash/chrome.20170816.110443.6220.meta'
Uploaded chrome-ptz.tar to https://drive.google.com/corp/drive/u/1/folders/0B8sYeJbsz9zKSEJDa1RSanh3TWM.
For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.
,
Aug 16 2017
,
Aug 16 2017
I'm not sure where this bug ought to go, but it's not an Infra bug.
,
Aug 23 2017
,
Aug 23 2017
,
Sep 18 2017
Moving to ChromeOS specific client component. Please provide more detail/justification if moved back to I>C>Chrome.
,
Sep 20 2017
mzhuo@ - is this still reproducible? Try it on M62 and M63 as well.
,
Sep 20 2017
mzhuo@ - please also post the sequence of telemetry commands / CFM API calls you are running when you see this issue.
,
Dec 1 2017
,
Jan 18 2018
,
Jan 18 2018
,
Mar 6 2018
Not reproducible in M64 or M65. |
|||||||||||
►
Sign in to add a comment |
|||||||||||
Comment 1 by mzhuo@chromium.org
, Aug 16 2017