Crash ID: 7bcae7ec00000000 

Able to reproduce the issue on Blaze using chrome version 52.0.2733.0/8315.0.0

crash id ::b2d41a0a00000000

Stack Trace
=====================
Thread 0 CRASHED [SIGSEGV @ 0x00000004 ] MAGIC SIGNATURE THREAD
0xb4c041be	(libblink_platform.so + 0x001151be )	
0xb4c7fef3	(libblink_platform.so + 0x00190ef3 )	
0xb4c7fed7	(libblink_platform.so + 0x00190ed7 )	
0xb4bc554b	(libblink_platform.so + 0x000d654b )	
0xb4bc5467	(libblink_platform.so + 0x000d6467 )	
0xb4cd0865	(libblink_platform.so + 0x001e1865 )	
0xb4cd095d	(libblink_platform.so + 0x001e195d )	
0xb4cd3845	(libblink_platform.so + 0x001e4845 )	
0xb4cd676f	(libblink_platform.so + 0x001e776f )	
0xb4df95d2	(libblink_platform.so + 0x0030a5d2 )	
0xb4ccee9f	(libblink_platform.so + 0x001dfe9f )	
0xafa99a87	(libscheduler.so + 0x00021a87 )	
0xb0e56bbd	(libgcc_s.so.1 -bpabi.c:41 )	__gnu_ldivmod_helper
0xffffffff		
0xb4f2dbc1	(libbase.so + 0x000cfbc1 )	
0xb4ed82fd	(libbase.so + 0x0007a2fd )	
0xb4ed82fd	(libbase.so + 0x0007a2fd )	
0xafa99a87	(libscheduler.so + 0x00021a87 )	
0xb4cd41c1	(libblink_platform.so + 0x001e51c1 )	
0xb4396686	(libcontent.so + 0x00dff686 )	
0xb4be3d47	(libblink_platform.so + 0x000f4d47 )	
0xafa9a1a9	(libscheduler.so + 0x000221a9 )	
0xafa9a177	(libscheduler.so + 0x00022177 )	
0xafa9a205	(libscheduler.so + 0x00022205 )	
0xafa9a1cb	(libscheduler.so + 0x000221cb )	
0xafa99dc9	(libscheduler.so + 0x00021dc9 )	
0xafaa2eba	(libscheduler.so + 0x0002aeba )	
0xb0e56bbd	(libgcc_s.so.1 -bpabi.c:41 )	__gnu_ldivmod_helper
0x000003e6		
0xafaa2eba	(libscheduler.so + 0x0002aeba )	
0xb0e4eb5f	(libgcc_s.so.1 + 0x0000eb5f )	__aeabi_ldivmod

Chrome crashed on device Jerry with M52 52.0.2739.0 / 8337.0.0 dev build as soon as hangout call was started. Though repro steps are different from the initial bug report, I am updating this bug as crash stack trace looks similar to comment#3.

Crash ID: 3dc92bca00000000, 2e67ebca00000000

gkihumba@ - is this another instance of missing symbols?

Yes these are missing symbols. See crbug/610902

srcv@: I've added your comment #4 to relevant bug about crashing hangouts (crbug/611585)

Stack traces are different, but could have same root cause as in both bugs hangouts crashes

Version 52.0.2743.41/ 8350.31.0 (Official Build) beta-channel veyron_minnie
Firmware Google_Veyron_Minnie.6588.197.0
Crash ID: a975773c00000000

There were no visible chrome crashes on device Minnie during apprt calls but Chrome://crashes shows a crash report (with ID mentioned above) during apprtc calls. Updating this bug as crash stack trace is similar to comment #3. 

Thread 0 CRASHED [SIGSEGV @ 0x00000000 ] MAGIC SIGNATURE THREAD
0xb4a59496	(chrome + 0x02358496 )	
0xb478e109	(chrome + 0x0208d109 )	
0xb478f24d	(chrome + 0x0208e24d )	
0xb478ae03	(chrome + 0x02089e03 )	
0xb5b6c2fd	(chrome + 0x0346b2fd )	
0xb478aeb3	(chrome + 0x02089eb3 )	
0xb478af9f	(chrome + 0x02089f9f )	
0xb47881af	(chrome + 0x020871af )	
0xb4788c71	(chrome + 0x02087c71 )	
0xb2b511cb	(chrome + 0x004501cb )	
0xb4788dd7	(chrome + 0x02087dd7 )	
0xb4a4807d	(chrome + 0x0234707d )	
0xb4a480a3	(chrome + 0x023470a3 )	
0xb4a1219b	(chrome + 0x0231119b )	
0xb4a122eb	(chrome + 0x023112eb )	
0xb4a121ff	(chrome + 0x023111ff )	
0xb4a122fb	(chrome + 0x023112fb )	
0xb4a07729	(chrome + 0x02306729 )	
0xb3635043	(chrome + 0x00f34043 )	
0xb4a1f5df	(chrome + 0x0231e5df )	
0xb2b3f257	(chrome + 0x0043e257 )	
0xb4a1ff1f	(chrome + 0x0231ef1f )	
0xb491c91b	(chrome + 0x0221b91b )	
0xb5974107	(chrome + 0x03273107 )	
0xb50c3bc5	(chrome + 0x029c2bc5 )	
0xb5265825	(chrome + 0x02b64825 )	
0xb5265687	(chrome + 0x02b64687 )	
0xb4bfe59f	(chrome + 0x024fd59f )	
0xb4bfe501	(chrome + 0x024fd501 )	
0xb1fd8bbd	(libgcc_s.so.1 -bpabi.c:41 )	__gnu_ldivmod_helper
0xb1fd0b5f	(libgcc_s.so.1 + 0x0000eb5f )	__aeabi_ldivmod
0xb317e911	(chrome + 0x00a7d911 )	
0xb659a393	(chrome + 0x03e99393 )	
0xb1fd0b5f	(libgcc_s.so.1 + 0x0000eb5f )	__aeabi_ldivmod
0xb26ffeae		
0xb2b512ab	(chrome + 0x004502ab )	
0xb2f76d8b	(chrome + 0x00875d8b )	
0xb65a9862	(chrome + 0x03ea8862 )	
0xb6756cae	(chrome + 0x04055cae )	
0xb4bfe501	(chrome + 0x024fd501 )	
0xb4a94cf3	(chrome + 0x02393cf3 )	
0xb5973fb1	(chrome + 0x03272fb1 )	
0xb4bffa35	(chrome + 0x024fea35 )	
0xb4a94f37	(chrome + 0x02393f37 )	
0xb4a94b11	(chrome + 0x02393b11 )	
0xb659c5ce	(chrome + 0x03e9b5ce )	
0xb20e1dd5	(libstdc++.so.6.0.20 -char_traits.h:259 )	std::basic_string<char, std::char_traits<char>, std::allocator<char> >::compare
0xb7caceaa		
0xb312fc81	(chrome + 0x00a2ec81 )	
0xb312fc03	(chrome + 0x00a2ec03 )	
0xb312ece9	(chrome + 0x00a2dce9 )	
0xb2e7e0a3	(chrome + 0x0077d0a3 )	
0xb1ece307	(libc-2.19.so -libc-start.c:285 )	__libc_start_main
0xb2b2ff3f	(chrome + 0x0042ef3f )	
0xb6588193	(chrome + 0x03e87193 )	
0xb2b51399	(chrome + 0x00450399 )	
0xb1fb84d3	(libpthread-2.19.so -pthread_barrierattr_setpshared.c:39 )	pthread_barrierattr_setpshared
0xb1ee04bb	(libc-2.19.so -cxa_atexit.c:101 )	__new_exitfn
0xb221a13b	(libgestures.so.0 + 0x0001813b )	
0xb20aad1b	(libstdc++.so.6.0.20 -basic_ios.h:276 )	std::ios_base::Init::Init
0xb2700906		
0xb26ea7b7	(ld-2.19.so -dl-init.c:36 )	_dl_init
0xb2e7df47	(chrome + 0x0077cf47 )	
0xb2e7df7b	(chrome + 0x0077cf7b )	
0xb65881d3	(chrome + 0x03e871d3 )	
0xb26ea9bf	(ld-2.19.so + 0x0000b9bf )	_dl_sort_fini

Albert do you know who would be the right owner for this?

For some reason crash/ isn't properly symbolizing the call stack. It's really hard to guess who the right owner should be.

jennyz@ can you try to repro locally and see if you can get a more useful stack?

Comment 12: yes we've been having issues with builders timing out while uploading crash symbols. Options are either to repro locally or manually upload symbols to crash for that device/ build using e.g.:

upload_symbols --yes --official_build gs://chromeos-image-archive/link-release/R52-8305.0.0/debug.tgz

First option is less painful.

I tried to install screencastify on my samus 8315.0.0/52.0.2773.0, I could not repro the crash, it looks like working well. 

I tried with apprtc app too, no repro on samus. I will need a little help from mtv QA team to catch the repro on device.

We have M52 RC today and will test the scenario(screencastify, apprtc) on veyron and zako boards

Tested apprtc calls on device Minnie with latest M52 beta ( 52.0.2743.49 / 8350.38.0). No crashes were observed during apprtc calls. 

Testing team could not reproduce on M52 RC build 8350.38.0 on minnie and zako.

Based on comments 17/18, removing release block label and marking this as won't fix. Feel free to reopen bug if you can repro it in other builds