New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 756159 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chrome crash when running telemetry api to start meeting and get_device with PTZ camera connected

Project Member Reported by mzhuo@chromium.org, Aug 16 2017

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.

 

Comment 1 by mzhuo@chromium.org, Aug 16 2017

Note: Manually joining meeting and leaving meeting multiple times there is no chrome crash.

Comment 2 by mzhuo@chromium.org, Aug 16 2017

Labels: Proj-Bluestreak
Components: -Infra>Client>Chrome
I'm not sure where this bug ought to go, but it's not an Infra bug.

Comment 4 by mzhuo@chromium.org, Aug 23 2017

Components: Infra>Client>Chrome

Comment 5 by mzhuo@chromium.org, Aug 23 2017

Labels: M-61

Comment 6 by efoo@chromium.org, Sep 18 2017

Components: -Infra>Client>Chrome Infra>Client>ChromeOS
Moving to ChromeOS specific client component. Please provide more detail/justification if moved back to I>C>Chrome.
Cc: achuith@chromium.org
Owner: mzhuo@chromium.org
Status: Assigned (was: Untriaged)
mzhuo@ - is this still reproducible? Try it on M62 and M63 as well.
mzhuo@ - please also post the sequence of telemetry commands / CFM API calls you are running when you see this issue.

Comment 9 by mzhuo@chromium.org, Dec 1 2017

Summary: Chrome crash when running telemetry api to start meeting and get_device with PTZ camera connected (was: Chrome crash when running telemetry api to start meeting and get_device with PTZ camera connected ‹ Prev 2 of 8 Next ›)
Labels: Proj-Hotrod
Cc: -harpreet@chromium.org
Status: WontFix (was: Assigned)
Not reproducible in M64 or M65.

Sign in to add a comment