Description of problem: $ chromium-browser --incognito Received signal 11 SEGV_MAPERR 000000000028 #0 0x7feb3ced8019 base::debug::CollectStackTrace() #1 0x7feb3ce05eb1 base::debug::StackTrace::StackTrace() #2 0x7feb3ced846a base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7feb3ced8a5e base::debug::(anonymous namespace)::StackDumpSignalHandler() #4 0x7feb31030e80 <unknown> #5 0x55b911ed9724 (anonymous namespace)::BindProcessNode() #6 0x55b911ed90b1 base::internal::Invoker<>::Run() #7 0x55b911ed8df0 service_manager::CallbackBinder<>::RunCallback() #8 0x55b911ed92a3 base::internal::Invoker<>::RunOnce() #9 0x7feb3ce706dd base::TaskAnnotator::RunTask() #10 0x7feb3ce7f8be base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl() #11 0x7feb3ce800e7 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() #12 0x7feb3ce2ac98 base::MessagePumpGlib::Run() #13 0x7feb3ce7b78f base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run() #14 0x7feb3ce56778 base::RunLoop::RunWithTimeout() #15 0x55b911da6af7 ChromeBrowserMainParts::MainMessageLoopRun() #16 0x7feb39ded149 content::BrowserMainLoop::RunMainMessageLoopParts() #17 0x7feb39ded235 content::BrowserMainRunnerImpl::Run() #18 0x7feb39dd5459 content::BrowserMain() #19 0x7feb3a83c211 content::RunBrowserProcessMain() #20 0x7feb3a83c479 content::ContentMainRunnerImpl::RunServiceManager() #21 0x7feb3a83c84f content::ContentMainRunnerImpl::Run() #22 0x7feb2fa5ae0a service_manager::Main() #23 0x7feb3a83a426 content::ContentMain() #24 0x55b911491325 ChromeMain #25 0x7feb30229f33 __libc_start_main #26 0x55b91149118e _start r8: 00001b65251ef000 r9: 00007ffdac4f7e98 r10: 00007ffdac5c0080 r11: 00000000071cc022 r12: 00001b6525784f00 r13: 00007ffdac4f7e5c r14: 00007ffdac4f7ed0 r15: 00007ffdac4f8068 di: 0000000000000040 si: 000055b914259260 bp: 00007ffdac4f7e40 bx: 0000000000000000 dx: 00001b6525d60e20 ax: 00001b6525418dc0 cx: 00001b6525d60e20 sp: 00007ffdac4f7df0 ip: 000055b911ed9724 efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000004 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000028 [end of stack trace] Calling _exit(1). Core file will not be generated. Version-Release number of selected component (if applicable): chromium-75.0.3770.100-2.fc30.x86_64 How reproducible: Always. Steps to Reproduce: Execute `chromium-browser --incognito` Actual results: Received signal 11 SEGV_MAPERR 000000000028 Expected results: A chromium incognito window. Additional info: Starting chromium and then opening an incognito window works fine. The package was updated this morning, chromium was not running then, the system hasn't been rebooted yet: Upgrade chromium-75.0.3770.100-2.fc30.x86_64 @updates Upgraded chromium-73.0.3683.86-2.fc30.x86_64 @@System Upgrade chromium-common-75.0.3770.100-2.fc30.x86_64 @updates Upgraded chromium-common-73.0.3683.86-2.fc30.x86_64 @@System Upgrade chromium-libs-75.0.3770.100-2.fc30.x86_64 @updates Upgraded chromium-libs-73.0.3683.86-2.fc30.x86_64 @@System Upgrade chromium-libs-media-75.0.3770.100-2.fc30.x86_64 @updates Upgraded chromium-libs-media-73.0.3683.86-2.fc30.x86_64 @@System
Hmm, I can't reproduce this on my end. Do you have any addons or plugins in use?
I proactively blocked the package from RPM Fusion that has a "Supersedes" reverse dependency on chromium-libs-media, so I'm only on Fedora-provided packages. Regarding addons, I will send you a list of the ones I have enabled in incognito mode.
Don't worry about it, I was able to reproduce it by trying repeatedly. 99% sure this is the fix: https://chromium.googlesource.com/chromium/src/+/00281713519dbd84b90d2996a009bf3a7e294435%5E%21/#F0
That was fast! Since I can always reproduce it, I'll let you know as soon as an upgrade is available. We had a short out-of-band discussion, it turns out that disabling all my extensions in incognito mode hides the problem under the rug, and enabling any one of them is enough for me to get the crash.
For me, chromium (not incognito) crashes on every start with the same traceback, making it completely unusable. Do you intend to rebuild with the fix?
You can install the packages from this scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=36003506 It worked for me, but it would be nice to have an update before the next chromium release.
FEDORA-2019-a1af621faf has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1af621faf
FEDORA-EPEL-2019-931a6c5c69 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-931a6c5c69
chromium-75.0.3770.100-3.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-931a6c5c69
chromium-75.0.3770.100-3.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-a1af621faf
chromium-75.0.3770.100-3.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d10f4cadee
chromium-75.0.3770.100-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
chromium-75.0.3770.100-3.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.
chromium-75.0.3770.100-3.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.