Exact same result here. Started happening with Chrome 54. 

OS: Ubuntu 14.04.5 LTS
Kernel: 4.4.0-42-generic #62~14.04.1-Ubuntu
Chrome version: 54.0.2840.71

Oct 22 12:15:40 josh-ThinkPad-T430 kernel: [159775.320254] Chrome_IOThread[2660]: segfault at ffffc0e41c400a44 ip 0000557e7f763163 sp 00007fb7260c53b0 error 5 in chrome[557e7c339000+6432000]

Confirmed also on Ubuntu 16.10,
Chrome Version 54.0.2840.71 (64-bit)

I've delete ~/.config/google-chrome and re-login, didn't help.

[ 1677.168086] Chrome_IOThread[3184]: segfault at ffffdfd657ba308f ip 00005570a2bcc163 sp 00007f03cc56d2f0 error 5 in chrome[55709f7a2000+6432000]

Are there any associated crash IDs in chrome:crashes?
If there are, please post them here to assist in debugging.

Haven't noticed any 

#4 Do you have crash reporting enabled?
Search in chrome:settings for "Automatically send usage statistics and crash reports to Google"

Same problem.

I've got these two crash IDs: 32d52a7b00000000, ad4f2a7b00000000

Issue 640682 has been merged into this issue.

Issue 656338 has been merged into this issue.

Issue 656491 has been merged into this issue.

This issue appears to have flown under the radar because all of the related issues kept getting falsely merged into  bug 527035  (which has a very innocuous sounding title).

Related crash info: 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%27do_free_with_callback%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#samplereports:5,productversion:1000

If enough users are getting hit by this issue, it may be serious enough to warrant a Linux-only stable-respin.

Crash IDs: 16f6667b00000000 and 63081c7b00000000 are from today.  

Previous crash IDs also from v54 within the last week: 32cde1ab00000000, 108d04bb00000000, e6aad72b00000000, fefc49d900000000, e4f4f02b00000000, ce18ded900000000, c84c9ad900000000, dc27d4d900000000, 9f1e71cb00000000

Add crash ID 1d16f67b00000000 which also happened just now, 10 minutes within re-launching Chrome.

Crash ID Chrome: 8f12b3ab00000000, 5ea87ebb00000000, ae57e8bb00000000, 8acc9f3b00000000

Exact same issue here, Crash dump id:    ffc4897b00000000

#15
Thank you for the crash id, that looks like the same issue.  Please star bug 656073 now to express your interest.

It looks like we already have a fix on ToT and a merge will be coming soon.  I don't think it will be hard to convince the release team to push a new Linux stable Chrome in the next few days, but I can't make any promises.

I noticed that when I had my Chomecast unplugged from my TV, the segfaults stopped. Makes sense because Google Chrome does sync with / talk to the Chromecasts in the house for awareness. I've now had the Chromecast unplugged for 4 hours and haven't had a segfault since.

@thomasanderson, it seems we do not have permission to view/star Issue 656073
Can you open it to be publicly viewable/starable?

> it seems we do not have permission to view/star Issue 656073
Can confirm the lack of permission.

Permission granted for any issue and thanks 

Thank you for your help

@allenbritt2448@gmail.com I also don't have permission to view or star issue 656073

Not sure about that. AFAIK, there are no Chromecasts on my network, and I'm still experiencing the problem.

Maybe there's a TV/device on your network that has built-in casting abilities

In regards to removing a Chromecast device from the network as a workaround: After ~8 hrs of the Chromecast offline, I finally had a segfault. But it's still much better than every 5-20 minutes.

I'm the person on 527035 that's been reporting constant crashes. Currently on Chromium 53.0.2785.143 and am not seeing the crashes, however current version of google-chrome-stable, google-chrome-beta, and google-chrome-unstable do exhibit the issue for me.

I'll give the Chromecast theory a try tomorrow at work by connecting to our guest network.

Also I cannot view 656073.

some crash ids:

6acfe9ab00000000
9b19c07b00000000
ada4663900000000
09e930bb00000000
40ec123900000000
519b90bb00000000
0c6690bb00000000
121310bb00000000
ffe6623900000000
32f020bb00000000

... and i have plenty more. I also cannot see bug 656073 so as to star it.

Seeing the same crashes every 10-15 minutes too with Chrome stable on Debian jessie.
Cannot view 656073, permission denied.

Here's some of my crash ids:

7abdcd2b00000000
0fcd30bb00000000
d17aa07b00000000
9109727b00000000
8cf3206b00000000
2cc3b06b00000000
accb9d7b00000000
da52dd7b00000000
46b4973900000000
91cd973900000000
3489573900000000
501a6cfb00000000

If 656073 is the official issue that we should be using and starring, then why can nobody see it?

Any news? This is _extremely_ annoying, and 656073 is still private.

A temporary fix that worked for me (because I don't use chrome cast) was to block ports 8008 and 8009 in my firewall. (Ports 8008 and 8009 are the ports Chrome uses for discovering Chromecasts.) But if I had any other programs using those ports they wouldn't work either... 

christop...@rooneyworks.com: That's the work around I'm using now since Chromium (which doesn't exhibit the bug yet) is having some problems working with Chromecasts anyway.

Just a quick update.  Unfortunately I'm unable to restrict bug 656073, however the bug has already been identified and fixed, and we're planning on pushing a new release on Monday.  Note that the schedule may change if we encounter any unexpected issues.

thomasanderson@chromium.org: That's great news. Could you please update this issue with the fixed version/build, so we all know when to test? Thanks.

rubin@ I don't know what version will be pushed at the moment because there may be other patches that get merged to 54.  All I can say is the version will be the one after 54.0.2840.71  (ie, the fourth number will be something larger than 71)

Issue 660686 has been merged into this issue.

Issue 661185 has been merged into this issue.

I'm having crashes AT LEAST once every 15 minutes. Usually more. There are at least a few Chromecasts on the network here, but I can't try removing them as its a work network and they're in use. A few crash ids since I enabled reporting:

843ae74700000000
352c874700000000
a39bca7900000000
f4241e1b00000000
4d2af94700000000
0034b94700000000

I experienced the issue regularly with version 54.0.2840.71 on Ubuntu 16.04 on a network with several Chromecasts. I upgraded to the recently-released 54.0.2840.90 earlier today and haven't had any segfaults yet...

I've been running google-chrome-unstable 56.0.2906.0 dev (64-bit) on Debian Sid for the current work day on a network with a dozen Chromecasts, and have not encountered this issue yet. 👍🦄🎉