Raj: Can you take a look at this please ?

What is the web-app that they are using? We need to reproduce it at our end to continue investigation.

The webapp is a private tool which will not be exposed. Is there no way to derive the cause of the issue from the logs that were sent?

Note: Crashes happened 2 or 3 times a day on stable at the time that Chrome 59 was the stable. For version 60 beta, it happened less. For version 60 stable, we have not attempted to gather too much data, but it still happens.

Could it be that the issue is cookie/cache related?
There seems to be correlation between clearing caches&cookies and getting less crashes

Dear Google,

Any progress on this topic? Any info we can provide to help?
We are still having crashes on live systems.

Hi , do we have any updates on this 

Crash links: 
https://crash.corp.google.com/browse?stbtiq=f0bab4a268000000
https://crash.corp.google.com/browse?stbtiq=5191a79ef8000000

Device reboot by itself sounds like a kernel crash.

Quick look at M61 log, there are webrtc/audio failures prior to chrome crash and device reboot.

In ui.20170725-113551:
...
[1:1468:0725/163731.576822:ERROR:acm_receiver.cc(49)] AcmReceiver::SetExtraDelay 8276
[1:3:0725/163731.850823:ERROR:track_audio_renderer.cc(67)] Not implemented reached in virtual void content::TrackAudioRenderer::OnRenderError()
...
[1:20:0725/164550.441792:ERROR:channel.cc(780)] Failed to unprotect video RTP packet: size=905, seqnum=54044, SSRC=3917361536
...
[723:723:0725/164558.665469:ERROR:device_event_log_impl.cc(156)] [16:45:58.664] Network: device_event_log.cc:117 @@@ Slow method: ../../../../../../../home/chrome-bot/chrome_root/src/chromeos/network/network_state_handler.cc:UpdateNetworkServiceProperty: 106ms

** Signal 6 from trusted code: pc=7fcdf90f549f

** Signal 6 from trusted code: pc=7fcdf90f549f
[723:11098:0725/165026.667936:ERROR:crash_handler_host_linux.cc(436)] Failed to write crash dump for pid 2812


In messages around that timestamp:
2017-07-25T16:45:38.631606+02:00 ERR cras_server[1161]: pcm_avail returned frames larger than buf_size: Plantronics .Audio 628 USB: USB Audio:0,0: 272680 > 262144 for 1 times
2017-07-25T16:46:09.345253+02:00 ERR cras_server[1161]: pcm_avail returned frames larger than buf_size: Plantronics .Audio 628 USB: USB Audio:0,0: 262981 > 262144 for 9 times
2017-07-25T16:46:44.279438+02:00 ERR cras_server[1161]: pcm_avail returned frames larger than buf_size: Plantronics .Audio 628 USB: USB Audio:0,0: 271960 > 262144 for 17 times
2017-07-25T16:47:16.784898+02:00 ERR cras_server[1161]: pcm_avail returned frames larger than buf_size: Plantronics .Audio 628 USB: USB Audio:0,0: 262846 > 262144 for 29 times
2017-07-25T16:47:33.456744+02:00 ERR session_manager[678]: [ERROR:object_proxy.cc(582)] Failed to call method: org.chromium.LibCrosServiceInterface.CheckLiveness: object_path= /org/chromium/LibCrosService: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
2017-07-25T16:47:48.797323+02:00 ERR cras_server[1161]: pcm_avail returned frames larger than buf_size: Plantronics .Audio 628 USB: USB Audio:0,0: 310694 > 262144 for 32 times
2017-07-25T16:48:13.312519+02:00 WARNING session_manager[678]: [WARNING:liveness_checker_impl.cc(68)] Browser hang detected!
2017-07-25T16:48:13.312559+02:00 WARNING session_manager[678]: [WARNING:liveness_checker_impl.cc(72)] Aborting browser process.

Chrome fails to respond to CheckLiveness (meaning UI thread hangs).

And the device rebooted after that.

2017-07-25T16:50:26.934849+02:00 WARNING crash_reporter[11121]: Received crash notification for chrome[3321] user 1000 (called directly)
==== device rebooted ===
2017-07-25T16:50:49.733028+02:00 INFO kernel: [    0.000000] Initializing cgroup subsys cpuset

Any experiments we can run to potentially solve this?
Do you suspect it is a hardware, driver, browser or OS issue? Or is that still too early to say?
Can you give any timeline on when we can expect a concrete outcome of the root cause analysis or even a solution?

@8: the device reboots because chrome repeatedly crashes. That's by design, the session manager does this. It's definitely not a kernel problem.

Re #10: The chrome crash lines in messages come after the liveness check failure. I could not see it is repeated and causing the device to reboot.

I now see the "stuck on bsd ring" lines. Maybe that indicates a GPU hang and causing chrome problems?

2017-07-25T11:42:49.906292+02:00 INFO kernel: [  422.926364] [drm] stuck on bsd ring
2017-07-25T11:42:49.906318+02:00 INFO kernel: [  422.926389] [drm] GPU crash dump saved to /sys/class/drm/card0/error
2017-07-25T11:42:49.906321+02:00 INFO kernel: [  422.926401] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
2017-07-25T11:42:49.906324+02:00 INFO kernel: [  422.926415] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
2017-07-25T11:42:49.906338+02:00 INFO kernel: [  422.926441] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
2017-07-25T11:42:49.906341+02:00 INFO kernel: [  422.926455] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.

Dear masters of all things Chrome,

Can you give any timeline on when we can expect a concrete outcome of the root cause analysis or even a solution?

You mentioned GPU being a potential issue. The 	Intel® HD-Graphics 5500 should be powerful enough for our purpose of having a video call, shouldnt it?

You also mention: the device reboots because chrome repeatedly crashes. Is there any indication that the cause of Chrome crashing is the web service in use?

Stéphane, can you please triage?

BSD ring crashes are video problems -> Pawel

Dear Engineers,

Thanks for all the effort you put in so far. Id like to wrap this up as this issue has been open for too long.
I see three scenarios still:
1. Its a chrome issue
2. Its a webapp issue
3. its a driver issue

Can we isolate the root cause to be in one of these three categories or not?

posciak@
Is there any update for this case?

Hi Ryuta/Thomas
- Considering that Eng has already looked at this and cannot figure this out for weeks, means that existing logging doesn't capture the complete failure root cause
- At this point, the only way to move this investigation forward is by getting some way to repro this issue.

Thomas
- Can you work with IDNow and ask them for a way to give us an end point which we can use for repro ?
- GPU related issues are not always due to power of the processor... its more about the graphics related code which can sometimes have bugs. 
- The crash signatures and the system logs unfortunately do not capture enough data and we need get developers to repro this in their environment so that they can figure out what steps to use to find more debugging info

Hey. Thanks for the update. Ill contact IDNow to see if they can help out.

 Issue 776072  has been merged into this issue.

Hi, Is there an update on this issue as the issue we raised in 776072 has been moved to here?

We are able to reproduce the crash using a web based video conferencing solution, but not should what additional information is required.

Dear all,

Thanks for the investigation so far. Since you cannot replicate the issue and we cannot do much to grant you testing access, I suggest we close this issue.

Cheers

We had given Google access to the web conferencing tool before they logged the  issue 776072 .  They were able to logon and reproduce the crash.  Is there someone that we need to create an account for so that they can do the testing that has testing access?

Hello!
This bug is receiving this notice because there has been no acknowledgment of its existence in quite a bit of time
- If you are currently working on this bug, please provide an update.
- If you are currently affected by this bug, please update with your current symptoms and relevant logs.

If there has been no updates provided by EOD Wednesday, 12/19/18 (5pm EST), this bug will be archived and can be re-opened at any time deemed necessary.

Thank you!

Due to lack of action this bug has been Archived. If work is still being done on this issue or you are still experiencing this issue please feel free to re-open with the appropriate information.