Bug 1942490 - Chromium dies few seconds after start
Summary: Chromium dies few seconds after start
Keywords:
Status: CLOSED DUPLICATE of bug 1938962
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 33
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-24 13:03 UTC by lejeczek
Modified: 2021-03-25 15:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-25 15:09:57 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description lejeczek 2021-03-24 13:03:04 UTC
Description of problem:

-> $ chromium-browser 
ATTENTION: default value of option allow_rgb10_configs overridden by environment.
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
[22619:22619:0324/125817.067324:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[22587:22605:0324/125819.915582:ERROR:cast_crl.cc(384)] CRL - Verification failed.
Received signal 11 SEGV_MAPERR 000000000054
#0 0x5568430c0529 base::debug::CollectStackTrace()
#1 0x556843023986 base::debug::StackTrace::StackTrace()
#2 0x5568430bff69 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7fb7fc06cd10 (/usr/lib64/libpthread-2.32.9000.so+0x13d0f)
#4 0x7fb7fa3abfa5 __strlen_avx2
#5 0x5568459a02ea cast_channel::KeepAliveHandler::HandleMessage()
#6 0x55684599facc cast_channel::KeepAliveDelegate::OnMessage()
#7 0x55684599ee6c cast_channel::CastTransportImpl::DoReadCallback()
#8 0x55684599f27f cast_channel::CastTransportImpl::OnReadResult()
#9 0x5568459a107e cast_channel::MojoDataPump::ReceiveMore()
#10 0x5568439d094d mojo::SimpleWatcher::OnHandleReady()
#11 0x556843084f72 base::TaskAnnotator::RunTask()
#12 0x55684309a12b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl()
#13 0x55684309ae16 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork()
#14 0x5568430ea5c1 base::MessagePumpLibevent::Run()
#15 0x556843099410 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run()
#16 0x55684306756c base::RunLoop::Run()
#17 0x556840e45c4a content::BrowserProcessSubThread::IOThreadRun()
#18 0x5568430aadb8 base::Thread::ThreadMain()
#19 0x5568430d31e6 base::(anonymous namespace)::ThreadFunc()
#20 0x7fb7fc0623f9 start_thread
#21 0x7fb7fa34bba3 __GI___clone
  r8: 0000000000000000  r9: 0000000000000000 r10: 00007ffff03f7080 r11: 0000000000000286
 r12: 00000dc59a068610 r13: 0000000000000054 r14: 00007fb7e61e2f30 r15: 00007fb7e61e3198
  di: 0000000000000054  si: 000055684a169567  bp: 00007fb7e61e2cc0  bx: 00000dc599202050
  dx: 0000000000000054  ax: 0000000000000100  cx: 0000000000000014  sp: 00007fb7e61e2c88
  ip: 00007fb7fa3abfa5 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.

More importantly - if ABRT should then a second problem is ABRT does not notice.

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

mesa-dri-drivers-20.3.4-2.fc33.x86_64
kernel-5.11.8-200.fc33.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Tom "spot" Callaway 2021-03-25 15:09:57 UTC

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


Note You need to log in before you can comment on or make changes to this bug.