New issue
Advanced search Search tips

Issue 821286 link

Starred by 1 user

Issue metadata

Status: Closed
Owner:
Closed: Oct 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

pyro: Chrome crash after video_WebRtcMediaRecorder

Project Member Reported by tfiga@chromium.org, Mar 13 2018

Issue description

Chrome Version: 67.0.3366.3
OS: 10482.0.0

Looks like some chrome process is crashing at test termination.

http://ubercautotest.corp.google.com/tko/retrieve_logs.cgi?job=//results/183008652-chromeos-test/chromeos6-row1-rack2-host7

Reproduced 2 times in last 9 runs.

From /var/log/messages:

2018-03-12T16:44:28.510586-07:00 INFO session_manager[27262]: [INFO:policy_store.cc(89)] Persisted policy to disk, path: /var/lib/whitelist/policy.1
2018-03-12T16:44:28.694826-07:00 INFO session_manager[27262]: [INFO:child_exit_handler.cc(77)] Handling 27855 exit.
2018-03-12T16:44:28.736945-07:00 INFO session_manager[27262]: [INFO:policy_store.cc(89)] Persisted policy to disk, path: /var/lib/whitelist/policy.1
2018-03-12T16:44:28.915684-07:00 INFO session_manager[27262]: [INFO:child_exit_handler.cc(77)] Handling 27930 exit.
2018-03-12T16:45:50.950291-07:00 ERR kernel: [  673.586803] i2c_designware i2c_designware.2: i2c_dw_handle_tx_abort: slave address not acknowledged (7bit mode)
2018-03-12T16:46:21.692456-07:00 WARNING kernel: [  704.328108] do_trap: 21 callbacks suppressed
2018-03-12T16:46:21.692495-07:00 INFO kernel: [  704.328129] traps: Chrome_ChildIOT[27836] trap int3 ip:597dfb1eae46 sp:7df38d19df80 error:0
2018-03-12T16:46:21.716845-07:00 INFO crash_reporter[28055]: libminijail[28055]: mount /dev/log -> /dev/log type ''
2018-03-12T16:46:21.734125-07:00 WARNING crash_reporter[28055]: [user] Received crash notification for chrome[27828] sig 5, user 1000 (developer build - not testing - always dumping)
2018-03-12T16:46:21.736581-07:00 INFO crash_reporter[28055]: State of crashed process [27828]: D (disk sleep)
2018-03-12T16:46:22.443421-07:00 INFO crash_reporter[28055]: Stored minidump to /var/spool/crash/chrome.20180312.164621.27828.dmp
2018-03-12T16:46:22.443834-07:00 INFO crash_reporter[28055]: Leaving core file at /var/spool/crash/chrome.20180312.164621.27828.core due to developer image
2018-03-12T16:46:22.448579-07:00 WARNING crash_reporter[28055]: [ARC] Received crash notification for chrome[27828] sig 5, user 1000 (ignoring - crash origin is not ARC)
2018-03-12T16:46:22.693315-07:00 WARNING kernel: [  705.328359] init: arc-kmsg-logger main process (27569) killed by TERM signal
2018-03-12T16:46:22.818132-07:00 INFO session_manager[27262]: [INFO:browser_job.cc(164)] Terminating process: exiting cleanly
2018-03-12T16:46:22.818168-07:00 INFO session_manager[27262]: [INFO:system_utils_impl.cc(94)] Sending 15 to 27337 as 1000
2018-03-12T16:46:22.818246-07:00 INFO session_manager[27262]: [INFO:system_utils_impl.cc(94)] Sending 15 to 27623 as 1000
2018-03-12T16:46:25.094839-07:00 INFO session_manager[27262]: [INFO:session_manager_service.cc(494)] SessionManagerService quitting run loop
2018-03-12T16:46:25.094923-07:00 INFO session_manager[27262]: [INFO:session_manager_service.cc(203)] SessionManagerService exiting

 

Comment 1 by tfiga@chromium.org, Mar 13 2018

Labels: M-67
Summary: pyro: Chrome crash after video_WebRtcMediaRecorder (was: pyro: Crash in video_WebRtcMediaRecorder)
It's caused by websocket.WebSocketTimeoutException:

File "/usr/local/telemetry/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py", line 524, in _EvaluateJavaScript
      self._runtime.Crash(context_id, timeout)

https://cs.corp.google.com/clankium/src/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py?q=chrome_inspector/inspector_backend.py&dr&l=520

Seems to be an infrastructure issue.

Comment 3 by tfiga@chromium.org, Mar 14 2018

Are you sure about this? To me it looked like the websocket timeout was because of that Chrome crash happening earlier.
Status: Assigned (was: Untriaged)
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
Status: Closed (was: Assigned)
Doesn't seem to be happening anymore.

Sign in to add a comment