Bug 1941271

Summary: chromium-browser crashes after few seconds
Product: [Fedora] Fedora Reporter: Florian "der-flo" Lehner <dev>
Component: chromiumAssignee: Tom "spot" Callaway <spotrh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 32CC: spotrh, tpopela, yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-21 17:45:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Florian "der-flo" Lehner 2021-03-21 09:48:16 UTC 
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:

Every time


Steps to Reproduce:
1. start chromium-browser
2. wait up to three seconds
3. <crash>

Actual results:



Expected results:
Chromium doesn't crash and can be used to browse the web.


Additional info:

chromium-80.0.3987.163-1.fc32.x86_64 : A WebKit (Blink) powered web browser
Repo        : fedora
Matched from:
Filename    : /usr/bin/chromium-browser

Linux test 5.10.22-100.fc32.x86_64 #1 SMP Tue Mar 9 17:40:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Received signal 11 SEGV_MAPERR 000000000054
#0 0x55c910c5c529 base::debug::CollectStackTrace()
#1 0x55c910bbf986 base::debug::StackTrace::StackTrace()
#2 0x55c910c5bf69 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f5ef32a1a90 (/usr/lib64/libpthread-2.31.so+0x14a8f)
#4 0x7f5ef156f285 __strlen_avx2
#5 0x55c91353beca cast_channel::KeepAliveHandler::HandleMessage()
#6 0x55c91353b6ac cast_channel::KeepAliveDelegate::OnMessage()
#7 0x55c91353aa4c cast_channel::CastTransportImpl::DoReadCallback()
#8 0x55c91353ae5f cast_channel::CastTransportImpl::OnReadResult()
#9 0x55c91353cc5e cast_channel::MojoDataPump::ReceiveMore()
#10 0x55c91156c92d mojo::SimpleWatcher::OnHandleReady()
#11 0x55c910c20f72 base::TaskAnnotator::RunTask()
#12 0x55c910c3612b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x55c910c36e16 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x55c910c865a1 base::MessagePumpLibevent::Run()
#15 0x55c910c35410 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x55c910c0356c base::RunLoop::Run()
#17 0x55c90e9e1c4a content::BrowserProcessSubThread::IOThreadRun()
#18 0x55c910c46db8 base::Thread::ThreadMain()
#19 0x55c910c6f1e6 base::(anonymous namespace)::ThreadFunc()
#20 0x7f5ef3296432 start_thread
#21 0x7f5ef150e6d3 __GI___clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00007ffc123b9080 r11: 00007ffc123b9090
 r12: 000014bc7dbc9310 r13: 0000000000000054 r14: 00007f5ee4995fd0 r15: 00007f5ee4996238
  di: 0000000000000054  si: 000055c917d04387  bp: 00007f5ee4995d60  bx: 000014bc7cef3050
  dx: 0000000000000054  ax: 0000000000000100  cx: 0000000000000014  sp: 00007f5ee4995d28
  ip: 00007f5ef156f285 efl: 0000000000010283 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000054
[end of stack trace]
Comment 1 Florian "der-flo" Lehner 2021-03-21 10:01:48 UTC 
Additional information about environment:

Thinkpad x250 in docking station (lid closed) and connected to external Monitor, Fedora 32 XFCE spin
Comment 2 Florian "der-flo" Lehner 2021-03-21 17:45:34 UTC 
I've updated the device to Fedora 33 and was no longer able to reproduce the issue.

$ uname -a
Linux x250 5.11.7-200.fc33.x86_64 #1 SMP Wed Mar 17 18:55:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
$ chromium-browser --version
Chromium 88.0.4324.182 Fedora Project


So I'm closing this report. Please don't hesitate to reopen it if needed.
Comment 3 Tom "spot" Callaway 2021-03-25 15:02:41 UTC 

*** This bug has been marked as a duplicate of bug 1938962 ***