Crash loading chrome with chromecast extension enabled |
|||||||
Issue descriptionBroken out from crbug.com/421231 - user getting the following crash loading chromium with the chromecast extension enabled. Received signal 11 SEGV_MAPERR 000000000010 #0 0x7f5cec221425 base::debug::StackTrace::StackTrace() #1 0x7f5cec22180b <unknown> #2 0x7f5cec54c390 <unknown> #3 0x5560453ccdc8 <unknown> #4 0x5560453cf656 <unknown> #5 0x5560453cfdf9 <unknown> #6 0x5560453d0143 <unknown> #7 0x7f5cec29c821 <unknown> #8 0x7f5cec222eea base::debug::TaskAnnotator::RunTask() #9 0x7f5cec24be90 base::MessageLoop::RunTask() #10 0x7f5cec24d97d base::MessageLoop::DeferOrRunPendingTask() #11 0x7f5cec24e83d <unknown> #12 0x7f5cec24f300 base::MessagePumpLibevent::Run() #13 0x7f5cec24af15 base::MessageLoop::RunHandler() #14 0x7f5cec275628 base::RunLoop::Run() #15 0x7f5cec2a1e36 base::Thread::ThreadMain() #16 0x7f5cec29c726 <unknown> #17 0x7f5cec5426ba start_thread #18 0x7f5cd5bf13dd clone r8: 000000000000002e r9: 0000556046e236ec r10: 0000000000000000 r11: 00007f5cd5c7ef50 r12: 00007f5cb8b8aff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f5cb8b8aeb0 di: 0000000000000000 si: 00007f5cb8b8aeb0 bp: 00007f5cb8b8af00 bx: 00007f5cb8b8aeb0 dx: 000000000000006a ax: 0000000000000000 cx: 00007f5c9000ac60 sp: 00007f5cb8b8ae60 ip: 00005560453ccdc8 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010 [end of stack trace] Calling _exit(1). Core file will not be generated. $ uname -a Linux shammash 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS" $ dpkg -l chromium-browser Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================= ii chromium-brows 59.0.3071.10 amd64 Chromium web browser, open-source Worked fine before.
,
Jul 13 2017
Sorry, can't provide repro steps as it's not my bug - see the original bug report that this issue was split out from (421231)
,
Jul 13 2017
Thank you for providing more feedback. Adding requester "jbanavatu@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
,
Jul 14 2017
Could you please provide the sample crash server I'd by navigating to chrome://crashes for further investigation of the issue. Thanks!!
,
Jul 14 2017
,
Jul 14 2017
I was the one reporting this; it happened on startup until I removed the chromecast extension folder. I can't think of anything more to add, but feel free to ask questions.
,
Jul 17 2017
I can confirm that I have exactly the same error. My chromium does not start anymore. For anyone having this same problem, the extensions are in a bit of a weird place. I did: ~/.config/chromium/Default/Extensions lot of directories with gibberish names, then: find -name chrome* to find the folder that contains the chromecast extension.
,
Nov 10 2017
Here's how to reproduce a crash when enabling chromecast. 1) chrome://flags/#media-router 2) "Load Media Router Component Extension" -> Enabled 3) Restart Chromium and notice the crash (several different crashes are possible!) To reset all settings: rm -rf ~/.config/chromium/ # or mv ~/.config/chromium ~/.config/chromium-bak Then you can try again. Crash message with extensions enabled and signed-in to Google: [10450:10450:0712/084603.545372:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) https://bugs.chromium.org/p/chromium/issues/detail?id=421231 Crash message from fresh Chromium: Received signal 11 SEGV_MAPERR 000000000010 #0 0x557bbc3dc826 <unknown> r8: 0000000000000001 r9: 00007f4320344850 r10: 0000557bc0e52330 r11: 00007f4320390f40 r12: 00007f42f0d06048 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f42f0d05f00 di: 0000000000000000 si: 00007f42f0d05f00 bp: 00007f42f0d05f50 bx: 00007f42f0d05f00 dx: 0000000044495547 ax: 0000104dc2c24720 cx: 0000000000000000 sp: 00007f42f0d05eb0 ip: 0000557bbb526798 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. I encountered these bugs while trying to enable casting from my Linux server to my Chromecast. chromium --version Chromium 62.0.3202.89 Latest Arch Linux Linux computer-machine-name 4.13.11-1-ARCH #1 SMP PREEMPT Thu Nov 2 10:25:56 CET 2017 x86_64 GNU/Linux
,
Nov 12 2017
I can confirm the same bug under Arch Linux after enabling 'Media Router Component Extension' Crash Log: ATTENTION: default value of option force_s3tc_enable overridden by environment. [28770:28770:1112/003535.740895:ERROR:background_mode_manager_aura.cc(13)] Not implemented reached in virtual void BackgroundModeManager::EnableLaunchOnStartup(bool) Received signal 11 SEGV_MAPERR 000000000010 #0 0x556e7cc48aa6 <unknown> r8: 0000000000000001 r9: 0000556e816bdaac r10: 0000556e816bdab0 r11: 0000000000000001 r12: 00007f21246b00c8 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f21246aff80 di: 0000000000000000 si: 00007f21246aff80 bp: 00007f21246affd0 bx: 00007f21246aff80 dx: 0000000000000004 ax: 00003bf8b734fc90 cx: 0000000000000000 sp: 00007f21246aff30 ip: 0000556e7bd91f18 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010 [end of stack trace] Calling _exit(1). Core file will not be generated. Version: Chromium 62.0.3202.62 Env: Linux xpsbean 4.13.8-1-ARCH #1 SMP PREEMPT Wed Oct 18 11:49:44 CEST 2017 x86_64 GNU/Linux
,
Nov 13 2017
To be clear: the message from background_mode_manager_aura.cc is not related to this crash. It's a benign message that is printed out any time you have a background mode extension installed.
,
Nov 13 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@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
,
Nov 13 2017
We're aware that there are some compatibility issues with some Linux distributions, but we've never been able to get enough information to reproduce or investigate, because Chromium does not have crash reporting enabled.
,
Dec 1 2017
unwesen and jan.murre are you also running Arch Linux?
,
Dec 5 2017
Per notes above, not able to repro with a crash report. May be related to bug 704210 which was also on Arch Linux and which has been addressed. Closing for now, please reopen if you see the same behavior in the latest version of Chromium |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by jbanavatu@chromium.org
, Jul 13 2017Labels: Needs-Feedback
3.0 MB
3.0 MB View Download