New issue
Advanced search Search tips

Issue 769709 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chromium crashes immediately after using "Cast"

Reported by entodo...@gmail.com, Sep 28 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Steps to reproduce the problem:
1. Connecect and cast to a Chromecast device
2. Stop casting and close browser
3. Open browser again
Crash happens after step 2 or 3

What is the expected behavior?
Browser should open normally.

What went wrong?
The browser cannot be reopened. It keeps crashing and the only workaround I found was to Delete the file in the profile folder.

Crashed report ID: No

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: Version 61.0.3163.100 (Developer Build) (64-bit)  Channel: stable
OS Version: Archlinux
Flash Version: None

This is the first time I'm using a Chromecast and it works properly with two Android devices. It is chromium on the laptop that is having problems.
 
Chromium cast crash.txt
1.1 KB View Download
Components: Internals>Cast
I tried resetting the ~/.config/chromium folder completely and the issue remained. Then after it started crashing immediately on start, I tried launching  from the terminal with `chromium --disable-extensions`. I got the following error in the terminal:
[26199:26227:1001/211656.937421:ERROR:socket_stream.cc(101)] Socket was disconnected, closing input stream
[26199:26227:1001/211656.937445:ERROR:socket_stream.cc(210)] Closing stream with result -100
but it didn't crash.
What's more is that once the browser was closed, I could open it normally without disabling extensions.
Labels: TE-NeedsTriageFromMTV
Adding the label 'TE-NeedsTriageFromMTV' as issue requires Chromecast device to triage.
Status: WontFix (was: Unconfirmed)
We've seen issues like this in some Linux-based Chromium distributions.  That looks to be the case here.  You should follow-up with the distro.

Sign in to add a comment