Browser crash on start-up when the flag load-media-router-component-extension is enabled.
Reported by
pauline....@gmail.com,
Mar 19 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/56.0.2924.76 Chrome/56.0.2924.76 Safari/537.36 Steps to reproduce the problem: 1. Go to chrome://flags and enable "load-media-router-component-extension" 2. Close your browser and restart it 3. Browser crashes on start-up What is the expected behavior? Browser should not crash. What went wrong? Error from the command line is as follows: :ERROR:background_mode_manager_aura.cc(14)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 56.0.2924.76 Channel: stable OS Version: 16.04 Flash Version: Shockwave Flash 21.0 r0 The result of this issue is that either Chromecast cannot work with Chromium (when the flag is not set to enable) or your browser crashes on startup (but casting is possible then - if the browser does not immediately crash e.g. if you try directly after setting the flag without re-launching Chromium). To solve the issue, go to ~/.config/chromium/Default/Extensions/ and remove (or rename) the folder which relates to Chromecast.
,
Mar 23 2017
Unable to reproduce this issue on Ubuntu 14.04 with chrome #56.0.2924.76 After enabling the "load-media-router-component-extension" and reloading, didn't observe any browser crash. Attaching a screen-cast for reference. pauline.lallinec@ could you please re-try the scenario on clean profile with no apps & extensions and let us know your observations. Thank You...
,
Mar 24 2017
Accessibility probably isn't the right component, any ideas on the right one? I don't know who owns the "media router component extension"
,
Mar 27 2017
@kklauri: is that Google Chrome as your chrome://version/ seems to suggest? The issue reported relates to Chromium. No problem with Google Chrome.
,
Mar 27 2017
Thank you for providing more feedback. Adding requester "kkaluri@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
,
Apr 27 2017
As per comment#4, Tested this issue on Ubuntu 16.04 using chromium reported version - 56.0.2924.76 , 57.0.2987.98 & latest build-60.0.3083.0 as per the steps mentioned in comment#0. No crash observed after restarting the chromiun=m browser ( after enabling the flag in comment#0). Could you please the same on the latest versions of chromium and update the thread with your observations. Please find the attached screencast for reference & let us know if we miss any steps to reproduce the issue. Thanks in advance..!!
,
Sep 9 2017
Got the same problem on Debian testing 64bit with Chromium version 60.0.3112.78 (Developer Build). Not sure if the presence of a Chromecast device on the network has an impact on it. (The CC is the reason I need the media router extension.)
,
Sep 9 2017
Checked and removing the Chromecast from the network does not solve the issue. In my case, the crash is not instant either. My steps to reproduce: 1. enable Media Router Extension in chrome://flags and restart. 2. start using browser... you can even use the Chromecast. 3. Undetermined time (minutes) later: Chromium crashes (typically when switching to a tab). 4. Chromium henceforth crashes immediately on startup (opens, asks if tabs should be restored and crashes without interaction). The only way to get out of this crash loop is to launch chromium --disable-extensions and disable the Media Router extension. Alternatively, deleting this extension via the filesystem also allows Chromium to start up (but you lose Chromecast functionality again): rm -r ~/.config/chromium/Default/Extensions/pkedcjkdefgpdelpbcmbmeomcjbeemfm
,
Sep 9 2017
P.S. (Sorry for the many notifications but there appears to be no edit function) The tab to switch to to cause the crash is one that offers casting (Plex, YouTube, ...). Chromium will reliably crash here after enabling the media router extension and then switching to one of those tabs. (and then get stuck in the crash after startup loop)
,
Oct 30 2017
,
Nov 9 2017
I have the same issue after I enable Media Router Extension flag (according to Archlinux Wiki, this is all that's needed to enable Chrome Cast support: https://wiki.archlinux.org/index.php/Chromium#Chromecasts_in_the_network_are_not_discovered) and I'm getting the following crash report after the Media Router extension is enabled: Received signal 11 SEGV_MAPERR 000000000010 #0 0x55714d9d9826 <unknown> r8: 0000000000000001 r9: 000055715244f32c r10: 000055715244f330 r11: 0000000000000001 r12: 00007fbe8097b048 r13: 0000000000000008 r14: 0000000000000008 r15: 00007fbe8097af00 di: 0000000000000000 si: 00007fbe8097af00 bp: 00007fbe8097af50 bx: 00007fbe8097af00 dx: 0000000000000004 ax: 000013e69d354990 cx: 0000000000000000 sp: 00007fbe8097aeb0 ip: 000055714cb23798 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010 [end of stack trace] Calling _exit(1). Core file will not be generated.
,
Dec 22 2017
Still having this issue in 62.0.3202.89 (on Debian buster/sid).
,
Dec 24
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by nyerramilli@chromium.org
, Mar 21 2017