Daniel, is this something you might be familiar with (or know someone whom is)?

I'm not really sure what's going on here: looks like the browser is getting killed by an external process? CCing some people who know more about the CrOS process model than me.

I'm not sure what to make of why it's getting SIGABRT in pthread_cond_timedwait either. Something I noticed in the crash report, is that all of the other threads are waiting too.

We are still seeing this, but we are not blocking stable on it at this point.

Seeing this in M52 stable 8350.68.0/52.0.2743.116

Report link:
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_ChromeOS%27%20AND%20product.version%3D%2752.0.2743.116%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27renderer%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27base%3A%3AConditionVariable%3A%3ATimedWait%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=231f932900000000&index=0#0

Any updates on this?

I'm really not the right person to investigate this. Someone who's familiar with the session manager on CrOS should probably triage this.

Issue 639625 has been merged into this issue.

Report ID75d2de5100000000 Still crashes on TOT 

Issue 652383 has been merged into this issue.

Reproduced same crash at M57(Chrome 57.0. 2984.0/Chrome OS: 9194.0.0)
ceash report:https://crash.corp.google.com/browse?stbtiq=5e05ad6580000000

https://crash.corp.google.com/browse?stbtiq=2f9d19d300000000

M-58 Enrolled Device

https://crash.corp.google.com/browse?stbtiq=17c772b300000000

This is ~20% of the crashes on the last 58 dev for parrot (Chrome OS), is there any progress here?

Fresh example on 57.0.2987.146 - https://crash.corp.google.com/browse?stbtiq=e5c78bf990000000

This signature is driving up crash rates for parrot on M61 beta to very high levels. Any updates?

Re #19: it is M60 Beta

This was reproduced at the ARC++ bug bash.  Play Store hung and the whole system was not responsive, machine was force rebooted.

https://crash.corp.google.com/browse?q=reportid=%274ced4d0140000000%27

one more carsh at M61. https://crash.corp.google.com/browse?stbtiq=561806f504000000

Reassigning to snanda@ per #10:  session manager on CrOS.   Can you help us reassign?  Thanks.

derat, would you have any insights into this?

session_manager sends SIGABRT to Chrome if it's not responding to D-Bus method calls. If you have the logs from a system where you saw this crash, you can check /var/log/messages to see if that happened here. I don't think that this is actionable based on the information that's here, though.

derat@ Is this helpful?

Here's a stack from a sample report:

Report ID2e5a4da4eb1a6f28
Product, versionChrome_ChromeOS, 61.0.3163.51
Process typegpu-process
Magic Signaturebase::ConditionVariable::TimedWait
(crbug 613226, bug 475616)edit bugs&comments
User bug(s): crbug 712691User entered feedback sent through Google feedback.
User Entered Descriptions (152)
Stable Signaturebase::ConditionVariable::TimedWait-517081bfedit bugs&comments
Report TimeTue, 22 Aug 2017 08:52:38 GMT
Uptime26028028 ms
Client ID1fc574a78ad2418e829683c63413ea0f
FilesminidumpDownloadReprocess this minidump
chrome.txtDownloadView file
Device Modelparrot-signed-mp-v4keys
Thread 0 (id: 1012) CRASHED [SIGABRT @ 0x000003e800000306 ] MAGIC SIGNATURE THREAD

	0x00007fc1e79a9848	(libpthread-2.23.so + 0x0000d848 )	pthread_cond_timedwait
0x00007fc1e8dc8a6f	(chrome -condition_variable_posix.cc:117 )	base::ConditionVariable::TimedWait(base::TimeDelta const&)
0x00007fc1e8dc8e6f	(chrome -waitable_event_posix.cc:223 )	base::WaitableEvent::TimedWaitUntil(base::TimeTicks const&)
0x00007fc1e8dc17f0	(chrome -message_pump_default.cc:59 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate*)
0x00007fc1eac17a85	(chrome -run_loop.cc:111 )	base::RunLoop::Run()
0x00007fc1ed75f4a1	(chrome -gpu_main.cc:300 )	content::GpuMain(content::MainFunctionParams const&)
0x00007fc1ea886f55	(chrome -content_main_runner.cc:686 )	content::ContentMainRunnerImpl::Run()
0x00007fc1ea8a9533	(chrome -main.cc:469 )	service_manager::Main(service_manager::MainParams const&)
0x00007fc1ea885fd0	(chrome -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const&)
0x00007fc1e902e69b	(chrome -chrome_main.cc:139 )	ChromeMain
0x00007fc1e65ff815	(libc-2.23.so -libc-start.c:289 )	__libc_start_main
0x00007fc1e902e508	(chrome + 0x0124e508 )	_start
0x00007ffe86ab9657		


Link: https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_ChromeOS%27%20AND%20product.version%3D%2761.0.3163.51%27%20AND%20custom_data.ChromeCrashProto.os_linux.lsb_release%20CONTAINS%20LOWER(%27PARROT%27)%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27base%3A%3AConditionVariable%3A%3ATimedWait%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&unnest=&stbtiq=&reportid=2e5a4da4eb1a6f28&index=0

Deleted: upload_file_minidump-2e5a4da4eb1a6f28.dmp 116 KB

upload_file_minidump-2e5a4da4eb1a6f28.dmp 116 KB Download

Deleted: chrome.txt-2e5a4da4eb1a6f28.gz 3.2 KB

chrome.txt-2e5a4da4eb1a6f28.gz 3.2 KB Download

Nope, I don't think so.

Observed this issue on M-61 build (9765.66.0, 61.0.3163.96 beta build) on eve, while sign in/sign out. Observed a browser crash.

Crash report: https://crash.corp.google.com/browse?stbtiq=40a6c40dadc315d4&sql_dialect=dremelsql#0

Observed this crash on M-63 build as well (10032.4.0/ 63.0.3239.7 dev build)

Observed in M64-BETA-CHROMEOS-2 (10176.22.0, 64.0.3282.41)

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_ChromeOS%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27base%3A%3AConditionVariable%3A%3ATimedWait%27%20AND%20product.Version%3D%2764.0.3282.41%27&sql_dialect=googlesql&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D&stbtiq=&reportid=&index=0