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

Issue 693269 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chrome crash after update applied

Project Member Reported by kuscher@chromium.org, Feb 16 2017

Issue description

Chrome Version       : 56.0.2924.101
OS Version: 9000.87.0

https://feedback.corp.google.com/#/Report/53431061443

Description:
1. Restarted to apply update.
2. System came back up but seemed slower
3. Went into chrome browser.
4. System crash

UI language:
en-US

Version:
57.0.2987.32 beta

Product Specific Data (whitelisted):
CHROME VERSION: 57.0.2987.32 beta
CHROMEOS_AUSERVER: <URL: 3>
CHROMEOS_RELEASE_BOARD: panther-signed-mp-v2keys
CHROMEOS_RELEASE_DESCRIPTION: 9202.18.0 (Official Build) beta-channel panther
CHROMEOS_RELEASE_TRACK: beta-channel
CHROMEOS_RELEASE_VERSION: 9202.18.0
ENTERPRISE_ENROLLED: Managed
expi:  3300109 3300132 3313322 3313327
hardware_class: PANTHER G5I-Z4A-A8L
 
Cc: dhadd...@chromium.org vsu...@chromium.org
2017-02-16T09:22:00.068957-08:00 INFO session_manager[857]: [INFO:browser_job.cc(157)] Terminating process: Browser did not respond to DBus liveness check.
2017-02-16T09:22:00.068964-08:00 INFO session_manager[857]: [INFO:system_utils_impl.cc(110)] Sending 6 to 890 as 1000
2017-02-16T09:22:00.139926-08:00 WARNING crash_reporter[4860]: Received crash notification for chrome[890] user 1000 (called directly)
2017-02-16T09:22:03.069195-08:00 WARNING session_manager[857]: [WARNING:browser_job.cc(165)] Aborting child process 890's process group 3 seconds after sending signal
2017-02-16T09:22:03.069209-08:00 INFO session_manager[857]: [INFO:browser_job.cc(149)] Terminating process group: Browser took more than 3 seconds to exit after signal.
2017-02-16T09:22:03.069215-08:00 INFO session_manager[857]: [INFO:system_utils_impl.cc(110)] Sending 6 to -890 as 1000
2017-02-16T09:22:03.175672-08:00 WARNING crash_reporter[4869]: [user] Received crash notification for chrome[1948] sig 6, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-02-16T09:22:03.388223-08:00 WARNING crash_reporter[4890]: [user] Received crash notification for chrome[2098] sig 6, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-02-16T09:22:03.392196-08:00 WARNING crash_reporter[4888]: Received crash notification for chrome-crash-unknown-process[3235] user 1000 (called directly)
2017-02-16T09:22:03.397676-08:00 WARNING crash_reporter[4892]: Received crash notification for chrome-crash-unknown-process[3923] user 1000 (called directly)
2017-02-16T09:22:03.404115-08:00 WARNING crash_reporter[4893]: Received crash notification for chrome[2098] user 1000 (called directly)
2017-02-16T09:22:03.414041-08:00 WARNING crash_reporter[4898]: [user] Received crash notification for chrome[2092] sig 6, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-02-16T09:22:03.536332-08:00 WARNING crash_reporter[4922]: Received crash notification for chrome-crash-unknown-process[3215] user 1000 (called directly)
2017-02-16T09:22:03.586771-08:00 WARNING crash_reporter[4935]: [user] Received crash notification for chrome[890] sig 6, user 1000 (ignoring call by kernel - chrome crash; waiting for chrome to call us directly)
2017-02-16T09:22:03.730750-08:00 INFO session_manager[857]: [INFO:child_exit_handler.cc(77)] Handling 890 exit.
2017-02-16T09:22:03.730763-08:00 ERR session_manager[857]: [ERROR:child_exit_handler.cc(85)]   Exited with signal 6
2017-02-16T09:22:03.730775-08:00 INFO session_manager[857]: [INFO:session_manager_service.cc(301)] Exiting process is chrome.
2017-02-16T09:22:03.730783-08:00 INFO session_manager[857]: [INFO:browser_job.cc(149)] Terminating process group: Ensuring browser processes are gone.
2017-02-16T09:22:03.730791-08:00 INFO session_manager[857]: [INFO:system_utils_impl.cc(110)] Sending 9 to -890 as 1000

Maybe https://bugs.chromium.org/p/chromium/issues/detail?id=634386 ?
Actually the prior messages are probably more helpful:

...
2017-02-16T09:21:31.659551-08:00 ERR chrome[890]: [890:890:0216/092131.659526:INFO:remote_commands_invalidator.cc(32)] Initialize RemoteCommandsInvalidator.
2017-02-16T09:21:31.659625-08:00 ERR chrome[890]: [890:890:0216/092131.659604:INFO:remote_commands_invalidator.cc(57)] Starting RemoteCommandsInvalidator.
2017-02-16T09:21:31.659711-08:00 ERR chrome[890]: [890:890:0216/092131.659687:INFO:remote_commands_invalidator.cc(123)] RemoteCommandsInvalidator ReloadPolicyData.
2017-02-16T09:21:31.659762-08:00 ERR chrome[890]: [890:890:0216/092131.659746:INFO:remote_commands_invalidator.cc(147)] Register RemoteCommandsInvalidator.
2017-02-16T09:21:31.659828-08:00 ERR chrome[890]: [890:890:0216/092131.659815:INFO:remote_commands_invalidator.cc(83)] RemoteCommandsInvalidator state changed: 3
2017-02-16T09:21:31.659980-08:00 ERR chrome[890]: [890:890:0216/092131.659962:INFO:remote_commands_invalidator.cc(83)] RemoteCommandsInvalidator state changed: 3
2017-02-16T09:21:36.022665-08:00 INFO chrome[890]: cras_client: remove stream 65536
2017-02-16T09:21:36.587144-08:00 DEBUG chrome[890]: cras_client: server_fd_state: disconnected
2017-02-16T09:21:46.025398-08:00 DEBUG chrome[890]: cras_client: server_fd_state: disconnected
2017-02-16T09:22:00.068936-08:00 WARNING session_manager[857]: [WARNING:liveness_checker_impl.cc(68)] Browser hang detected!
2017-02-16T09:22:00.068948-08:00 WARNING session_manager[857]: [WARNING:liveness_checker_impl.cc(72)] Aborting browser process.
...
Labels: -ReleaseBlock-Beta ReleaseBlock-Stable
Labels: -ReleaseBlock-Stable ReleaseBlock-Beta
zzzz
Does it keep crashing or just a once off?
I does not look like a continuos crash as per reports in the server:
https://crash.corp.google.com/browse?q=product.Version%3D%2757.0.2987.32%27%20AND%20ClientID%3D%27F649EB285BCF4763958C74A50A91773D%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-samplereports:5,-productname,productversion,magicsignature,processuptime,clientid,hour

There are 5 reports today
3 with no symbols 
1 base::UnixDomainSocket::RecvMsgWithFlags -> issue 512070
1 epoll_dispatch -> not new crash, similar to  issue 684917 

Status: WontFix (was: Unconfirmed)
All of the crashes reported on this device reference known issues that are being actively worked on.

Sign in to add a comment