Don't have a set up with Chrome-cast available to verify this and confirm if this has regressed or not.

Requesting someone from respective team to have a look into this and confirm the behavior.

Cast support is not enabled by default in Chromium.   It can be re-enabled by setting load-media-router-component-extension to "enabled" in chrome://flags and restarting the browser.

That flag was already set to "enabled". Is there a way to debug that functionality?

Thank you for providing more feedback. Adding requester "mfoltz@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

FYI I've retested this with the latest available version, "chromium-browser (57.0.2987.98-0ubuntu0.16.04.1276)".

Now, when the "load-media-router-component-extension" flag is enabled, Chromium crashes immediately upon startup with a segfault. I'm not sure how to get better debug information because this doesn't tell me a lot:

```
Thread 42 "Networking Priv" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff349ed700 (LWP 18396)]
0x0000555555c83bf8 in ?? ()
(gdb) bt
#0  0x0000555555c83bf8 in ?? ()
#1  0x0000555555c851b1 in ?? ()
#2  0x0000555555c85819 in ?? ()
#3  0x0000555555c85da7 in ?? ()
#4  0x00007ffff7923cd4 in ?? () from /usr/lib/chromium-browser/./libbase.so
#5  0x00007ffff78af133 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () from /usr/lib/chromium-browser/./libbase.so
#6  0x00007ffff78d4f50 in base::MessageLoop::RunTask(base::PendingTask*) () from /usr/lib/chromium-browser/./libbase.so
#7  0x00007ffff78d6b4d in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) () from /usr/lib/chromium-browser/./libbase.so
#8  0x00007ffff78d79ad in base::MessageLoop::DoWork() () from /usr/lib/chromium-browser/./libbase.so
#9  0x00007ffff78d8410 in base::MessagePumpLibevent::Run(base::MessagePump::Delegate*) () from /usr/lib/chromium-browser/./libbase.so
#10 0x00007ffff78d4332 in base::MessageLoop::RunHandler() () from /usr/lib/chromium-browser/./libbase.so
#11 0x00007ffff78fee38 in base::RunLoop::Run() () from /usr/lib/chromium-browser/./libbase.so
#12 0x00007ffff7928df6 in base::Thread::ThreadMain() () from /usr/lib/chromium-browser/./libbase.so
#13 0x00007ffff7923bf6 in ?? () from /usr/lib/chromium-browser/./libbase.so
#14 0x00007ffff7bc16ba in start_thread (arg=0x7fff349ed700) at pthread_create.c:333
#15 0x00007fffe24c782d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
```

denpashogai@: Would you be able to generate a minidump of the crash? See instructions in https://chromium.googlesource.com/chromium/src/+/master/docs/linux_crash_dumping.md#How-to-test-Breakpad-support-in-Chromium. Unfortunately I wasn't able to repro this issue locally. Hopefully the minidump can provide more info.

Sure, I hope there's something useful in there.

Deleted: 36f42cee-6d4b-18e6-25bb42b6-0355ae75.dmp 682 KB

36f42cee-6d4b-18e6-25bb42b6-0355ae75.dmp 682 KB Download

Unfortunately I have realized that it isn't so easy for me to try to debug the minidump; the binary and debug symbols included in your Linux distro isn't the same as "vanilla" Chromium. Because I couldn't repro this on Chrome, I suspect this might be an issue related to the distro. I would suggest trying to get a complete stack trace by using the instructions in https://wiki.ubuntu.com/Chromium/Debugging and installing the chromium-browser-dbgsym package. Sorry for the inconvenience; hopefully the instructions provided there can help get to the bottom of the crash.

It might be possible to build the package from source with debug symbols as well; but the instructions on the wiki page sound easier as a first try.

Thanks. Unfortunately it seems like the Ubuntu package of debugging symbols for Chromium is almost a year out of date and so refuses to install:

```
$ sudo apt-get install chromium-browser-dbg
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 chromium-browser-dbg : Depends: chromium-browser (= 51.0.2704.79-0ubuntu0.16.04.1.1242) but 57.0.2987.98-0ubuntu0.16.04.1276 is to be installed
E: Unable to correct problems, you have held broken packages.
```

This suggests that the only alternative is to build from source. I'll give that a shot, but foresee dependency hell.

Hi all. I managed to obtain and build Chromium from source, which took about 24 hours on my laptop (!) and used up about 32 gigs of space on my SSD. Nice.

When I ran the newly-built Chromium, it used my existing profile and *did not* crash with the media router extension. It picked up my Chromecast and had no problem casting video from YouTube... however, it runs extremely slow with a bunch of tabs open, perhaps because of the extra debugging stuff built in?

Anyway, the fact that the version I built from source works fine with the Chromecast suggests that either:

1. The Ubuntu repository build added something that causes a segfault when the media router component is enabled, or...
2. There was an important fix between the latest Ubuntu version "57.0.2987.98-0ubuntu0.16.04.1276" and the latest source version "60.0.3074.0 (Developer Build) (64-bit)", that stops the crash from happening.

Since the Ubuntu version is bad and the source build maxes out my four CPU cores almost constantly, can you suggest some steps from here to solve this? Thanks!

Another update, this time with better news: I did a distro update to Ubuntu 17.04, and the latest Chromium build there (57.0.2987.98-0ubuntu1.1348) works just fine again! Yay.

Thanks for the update, closing the issue.