Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1938962 - Received signal 11 SEGV_MAPERR 000000000058
Summary: Received signal 11 SEGV_MAPERR 000000000058
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 33
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1941271 1941527 1942490 1943944 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-15 11:07 UTC by Pierguido Lambri
Modified: 2021-04-16 16:12 UTC (History)
9 users (show)

Fixed In Version: chromium-89.0.4389.90-3.fc33 chromium-89.0.4389.90-3.fc34 chromium-89.0.4389.90-3.fc32 chromium-89.0.4389.90-3.el7 chromium-89.0.4389.90-3.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-01 01:50:38 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Pierguido Lambri 2021-03-15 11:07:27 UTC 
Description of problem:
Chromium crashes just after few clicks.

Version-Release number of selected component (if applicable):
chromium-89.0.4389.82-1.fc33.x86_64

How reproducible:
Always on this notebook

Steps to Reproduce:
1. Open chromium
2. Go to Fedora webpage and navigate through some links
3.

Actual results:
Chromium crashes.

Expected results:
Chromium should not crash

Additional info:
Downgrading to 88.0.4324.182-2.fc33 fixes it.
Comment 1 Pierguido Lambri 2021-03-15 11:09:50 UTC 
This is the backtrace I get.
I wasn't able to make abrt report this for some reasons. Tried some random switches (--disable-gpu and --no-sandbox) but no changes.


❯ chromium-browser
[13209:13245:0315/104243.312166:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.Notifications.GetCapabilities: object_path= /org/freedesktop/Notifications: org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate re
mote peer.
ATTENTION: default value of option allow_rgb10_configs overridden by environment.
[13242:13242:0315/104243.809538:ERROR:viz_main_impl.cc(150)] Exiting GPU process due to errors during initialization
Received signal 11 SEGV_MAPERR 000000000058
#0 0x563436715529 base::debug::CollectStackTrace()
#1 0x563436678986 base::debug::StackTrace::StackTrace()
#2 0x563436714f69 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f40810031e0 (/usr/lib64/libpthread-2.32.so+0x141df)
#4 0x7f407f28002a __GI___strlen_sse2
#5 0x563438ff52ea cast_channel::KeepAliveHandler::HandleMessage()
#6 0x563438ff4acc cast_channel::KeepAliveDelegate::OnMessage()
#7 0x563438ff3e6c cast_channel::CastTransportImpl::DoReadCallback()
#8 0x563438ff427f cast_channel::CastTransportImpl::OnReadResult()
#9 0x563438ff607e cast_channel::MojoDataPump::ReceiveMore()
#10 0x56343702594d mojo::SimpleWatcher::OnHandleReady()
#11 0x5634366d9f72 base::TaskAnnotator::RunTask()
#12 0x5634366ef12b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x5634366efe16 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x56343673f5c1 base::MessagePumpLibevent::Run()
#15 0x5634366ee410 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x5634366bc56c base::RunLoop::Run()
#17 0x56343449ac4a content::BrowserProcessSubThread::IOThreadRun()
#18 0x5634366ffdb8 base::Thread::ThreadMain()
#19 0x5634367281e6 base::(anonymous namespace)::ThreadFunc()
#20 0x7f4080ff83f9 start_thread
#21 0x7f407f2e1b53 __GI___clone
  r8: 0000000000000000  r9: 00003fe032529030 r10: 00007ffcaa3c4080 r11: 00007f407f378450
 r12: 00003fe031e6ef10 r13: 0000000000000058 r14: 00007f406b178f30 r15: 00007f406b179198
  di: 0000000000000058  si: 000056343d7be587  bp: 00007f406b178cc0  bx: 00003fe0329c2870
  dx: 0000000000000019  ax: 0000000000000058  cx: 0000000000000058  sp: 00007f406b178c88
  ip: 00007f407f28002a efl: 0000000000010293 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000058
[end of stack trace]
Calling _exit(1). Core file will not be generated.
Comment 2 Tom "spot" Callaway 2021-03-15 19:23:56 UTC 
Is this running normally in a bare-metal Fedora 33 x86_64 install? Please tell me as much as you can about the environment, hardware, and anything that might be unique or configured differently from the default.
Comment 3 Pierguido Lambri 2021-03-15 23:08:02 UTC 
The crash happens on a Lenovo T430s, a Fedora installation that, if I remember correctly, was updated from Fedora 32.
The crash happens either locally running in a normal Gnome env or remotely through ssh.
I just tried now on my desktop (AMD build) and got a similar crash:

❯ chromium-browser
ATTENTION: default value of option allow_rgb10_configs overridden by environment.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[1075594:1075594:0315/225939.815591:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[1075560:1075560:0315/225940.342389:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: Could not establish connection. Receiving end does not exist.", source: chrome-extension://mlnnopicjonfamklpcdfnbcomdlopmof/newtab.html (0)
Received signal 11 SEGV_MAPERR 000000000054
#0 0x557923c6d529 base::debug::CollectStackTrace()
#1 0x557923bd0986 base::debug::StackTrace::StackTrace()
#2 0x557923c6cf69 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f8367c251e0 (/usr/lib64/libpthread-2.32.so+0x141df)
#4 0x7f8365f64605 __strlen_avx2
#5 0x55792654d2ea cast_channel::KeepAliveHandler::HandleMessage()
#6 0x55792654cacc cast_channel::KeepAliveDelegate::OnMessage()
#7 0x55792654be6c cast_channel::CastTransportImpl::DoReadCallback()
#8 0x55792654c27f cast_channel::CastTransportImpl::OnReadResult()
#9 0x55792654e07e cast_channel::MojoDataPump::ReceiveMore()
#10 0x55792457d94d mojo::SimpleWatcher::OnHandleReady()
#11 0x557923c31f72 base::TaskAnnotator::RunTask()
#12 0x557923c4712b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x557923c47e16 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x557923c975c1 base::MessagePumpLibevent::Run()
#15 0x557923c46410 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x557923c1456c base::RunLoop::Run()
#17 0x5579219f2c4a content::BrowserProcessSubThread::IOThreadRun()
#18 0x557923c57db8 base::Thread::ThreadMain()
#19 0x557923c801e6 base::(anonymous namespace)::ThreadFunc()
#20 0x7f8367c1a3f9 start_thread
#21 0x7f8365f03b53 __GI___clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00007fff2ff41080 r11: 00007fff2ff41090
 r12: 000004dccdc2e710 r13: 0000000000000054 r14: 00007f835effdf30 r15: 00007f835effe198
  di: 0000000000000054  si: 000055792ad16567  bp: 00007f835effdcc0  bx: 000004dcd2d23000
  dx: 0000000000000054  ax: 0000000000000100  cx: 0000000000000014  sp: 00007f835effdc88
  ip: 00007f8365f64605 efl: 0000000000010283 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000054
[end of stack trace]
Calling _exit(1). Core file will not be generated.


This desktops runs a wayland env, sway WM, zsh as shell plus maybe some rust processes for shell customisation.
Not sure if you need more.
Comment 4 Tom "spot" Callaway 2021-03-25 15:02:35 UTC 
*** Bug 1941527 has been marked as a duplicate of this bug. ***
Comment 5 Tom "spot" Callaway 2021-03-25 15:02:39 UTC 
*** Bug 1941271 has been marked as a duplicate of this bug. ***
Comment 6 Tom "spot" Callaway 2021-03-25 15:04:35 UTC 
Gentoo has a fix for this crash. I am trying to get it built, but libva got updated at the same time in F34+ and that broke chromium. I have a fix for _that_ now, so new builds are happening. Also, I can't do more than three builds of Chromium at a time or koji never lets them finish.

Basically, what I'm saying is that I know this bug is here, a fix is coming as soon as possible, please be patient (and/or watch koji for new builds).
Comment 7 Tom "spot" Callaway 2021-03-25 15:09:55 UTC 
*** Bug 1942490 has been marked as a duplicate of this bug. ***
Comment 8 Peter Robinson 2021-03-25 15:12:36 UTC 
Perfect, thanks for the update spot
Comment 9 Fedora Update System 2021-03-29 17:55:30 UTC 
FEDORA-2021-78547312f2 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-78547312f2
Comment 10 Fedora Update System 2021-03-29 17:55:31 UTC 
FEDORA-EPEL-2021-b26bce013a has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b26bce013a
Comment 11 Fedora Update System 2021-03-29 17:55:32 UTC 
FEDORA-2021-141d8640ce has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2021-141d8640ce
Comment 12 Fedora Update System 2021-03-29 17:55:34 UTC 
FEDORA-EPEL-2021-d0a9c2bf03 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d0a9c2bf03
Comment 13 Tom "spot" Callaway 2021-03-29 18:02:29 UTC 
*** Bug 1943944 has been marked as a duplicate of this bug. ***
Comment 14 Mike Eddy 2021-03-30 11:43:25 UTC 
May still be happening?

Received signal 11 SEGV_MAPERR 000000000054

chromium.x86_64    89.0.4389.90-1.fc35    @rawhide
Comment 15 Peter Robinson 2021-03-30 11:54:10 UTC 
> chromium.x86_64    89.0.4389.90-1.fc35    @rawhide

You want chromium-89.0.4389.90-3 (not -1)
Comment 16 Fedora Update System 2021-03-30 14:38:42 UTC 
FEDORA-2021-78547312f2 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-78547312f2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-78547312f2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 17 Fedora Update System 2021-03-30 14:46:16 UTC 
FEDORA-EPEL-2021-b26bce013a has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-b26bce013a

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 18 Fedora Update System 2021-03-30 14:52:05 UTC 
FEDORA-EPEL-2021-d0a9c2bf03 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2021-d0a9c2bf03

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 19 Fedora Update System 2021-03-30 15:18:40 UTC 
FEDORA-2021-141d8640ce has been pushed to the Fedora 32 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-141d8640ce`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-141d8640ce

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 20 Fedora Update System 2021-03-30 15:21:26 UTC 
FEDORA-2021-4740239e28 has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-4740239e28`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4740239e28

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 21 Fedora Update System 2021-04-01 01:50:38 UTC 
FEDORA-2021-4740239e28 has been pushed to the Fedora 33 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 22 Fedora Update System 2021-04-05 00:16:47 UTC 
FEDORA-2021-78547312f2 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 23 Fedora Update System 2021-04-07 15:26:06 UTC 
FEDORA-2021-141d8640ce has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 24 Fedora Update System 2021-04-14 14:12:34 UTC 
FEDORA-EPEL-2021-d0a9c2bf03 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 25 Fedora Update System 2021-04-14 14:26:45 UTC 
FEDORA-EPEL-2021-b26bce013a has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.
Comment 26 Mike Eddy 2021-04-16 16:12:08 UTC 
When will this fix get into rawhide?

The latest version still seems to be chromium.x86_64 89.0.4389.90-1.fc35
Note You need to log in before you can comment on or make changes to this bug.