As detailed in the forum link above, my issue is a similar dmesg entry:

[626615.984917] BrowserBlocking[10585]: segfault at 0 ip 00007f095690f960 sp 00007f093d028ed0 error 4 in ld-2.17.so[7f0956906000+23000]

... but not directly related to any known action; the browser window disappears within about a minute after start.  I suspect a possible issue with my Google account, and will try to test 53.0.2785.116 with my account on a different machine (which is running successfully so far; upgraded today, about the same time as mine.)  I'll also try with no account login on this machine (a Lenovo ThinkPad T440p, Slackware64 14.1, Linux 3.16.2.)

Same here, I have recorded a video of the crash behaviour. Linked here: https://www.youtube.com/watch?v=1fiVzrKr3es

Running: Version 54.0.2840.59 (64-bit)
On: Linux tower 4.7.6-1-ARCH #1 SMP PREEMPT 
chrome://flags has  #media-router set to Default.

The output on console from google-chrome is as follows;

[19582:19582:1013/081546:ERROR:CONSOLE(1)] "Uncaught ReferenceError: media_router is not defined", source:  (1)
[1010:1067:1013/081554:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[19582:19582:1013/081601:ERROR:CONSOLE(437)] "Uncaught TypeError: Cannot read property 'updateMaxDialogHeight' of null", source: chrome://media-router/media_router.js (437)
[1010:1067:1013/081605:ERROR:ffmpeg_demuxer.cc(1595)] OnReadFrameDone result=-541478725 IsMaxMemoryUsageReached=0
[19582:19582:1013/081609:ERROR:CONSOLE(1)] "Uncaught ReferenceError: media_router is not defined", source:  (1)
Cannot upload crash dump: cannot exec /usr/bin/wget

Failed to get crash dump id.
Report Id:
[1]    19582 segmentation fault (core dumped)  google-chrome-stable

Here's a second video, of the same issue, but with slightly different behaviour. I have wget installed now, so I think the crash handler/uploader feature actually uploaded a core dump to google.

https://www.youtube.com/watch?v=-27Tw3wrePQ

Logs from console:
--2016-10-13 08:35:29--  https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 24.244.19.180, 24.244.19.183, 24.244.19.184, ...
Connecting to clients2.google.com (clients2.google.com)|24.244.19.180|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/dev/fd/3’


     0KCrash dump id:  9ae2115b00000000
                                                      1.33M=0s

[1]    25832 segmentation fault (core dumped)  google-chrome-stable

This is a regression in M53. Below is the crash rate for M53 & crash still exist in M54 and M55 also.

53.0.2785.143	19.95%	73	

Regression Range
================
https://chromium.googlesource.com/chromium/src/+log/53.0.2769.0..53.0.2774.0?pretty=fuller&n=10000

Possible suspect
================
https://chromium.googlesource.com/chromium/src/+/546cbaa96e356990ae1bb801d720025ca814812c

Link to the builds which introduced the crash.
==============================================
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Linux%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27WindowCapturerLinux%3A%3ACapture%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000,osversion,url,experiments

Assigning to the CL owner, please get this fixed before M55 hits Stable to avoid spikes in future.

sergeyu@ can we know what's the status of the fix since it's marked as RB-Stable,and we are about to promote M55 to Beta, so we need to get the fix into branch soon on 19th-oct.

Thanks!

Issue 657377 has been merged into this issue.

sergeyu@: Gentle Ping, Instances are reported on M55 Builds, but so far no instances reported on Market Beta 55.0.2883.21. Kindly have a look into it and please provide an update on the same.

Instances with Magic Signature: "WindowCapturerLinux::Capture" are currently observed on LinuX OS.

Below link gives in detail for the total number of instances in which the crash has occurred for associated builds:

https://crash.corp.google.com/browse?q=custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27WindowCapturerLinux%3A%3ACapture%27%20AND%20product.name%3D%27Chrome_Linux%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000

Can confirm that the issue still occurs in Beta 55.0.2883.21.

Crash dump id: a8eed73900000000

Crash also occurs in 56.0.2897.0-1

Crash dump id:  cf3b337b00000000

Stack Trace : go/crash/a8eed73900000000
-----------------------------------------

According to crash server comment #9 crash seems to be different while comparing with comment #8, Since this crash is observed on M53 builds confirming that comment #8 crash ID is a valid one where comment #9 crash is a observed only on latest M56.

This issue first seen on M53-53.0.2774.3, Below link gives in details of the number of instances in which the crash has occurred for associated builds:
https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Linux%27%20%20AND%20custom_data.ChromeCrashProto.ptype%3D%27browser%27%20AND%20custom_data.ChromeCrashProto.magic_signature_1.name%3D%27WindowCapturerLinux%3A%3ACapture%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000

As of now no crashes observed on latest beta, dev and canary channels. Crash is observed only on M54-56.0.2899.0 with 4 instances.
	
sergeyu@ - Since this issue is marked as stable blocker, can we get any update on this issue?

It looks like the problem is that the capturer doesn't handle the case when XGetPixmap() returns NULL. The regression is caused by https://codereview.webrtc.org/2044693002/, which causes XGetPixmap() to be called in some cases when it wouldn't be called previously.
This is easy to fix, but I'm not sure it's worth blocking stable on this issue.

Pending fix: https://codereview.webrtc.org/2446733003/

**** Bulk edit -  please ignore if not applicable ****

A friendly reminder that M55 Stable is launch is coming soon! Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP so it gets enough baking time in Beta (before Stable promotion). Thank you!

Your change meets the bar and is auto-approved for M55 (branch: 2883)

Is this change merged to M55?

Yes, merged to M55 WebRTC branch: https://chromium.googlesource.com/external/webrtc/trunk/webrtc/+/19a22c8fb88286f1ef2f487c8f97be9752f72bec

Thank you sergeyu@.
Applying "merge-merged-55" label and removing "Merge-Approved-55" label.

Not sure how the apt gets filled, but it missed the latest build of google-chrome-beta (which happened earlier today). If someone is able to kick off a rebuild of that deploy, I can test it out to confirm the fix.

The fix will be available with next week beta (tentative release on Wednesday). 

d'oh, just missed it for this week!

Verified in M56 56.0.2924.11 in Linux - no crashes seen while attempting to screenshare in hangouts

A fix seems to have made it out to 54 as well. Either that or a fix came down on the Linux side.

Issue 655664 has been merged into this issue.