Bug 1941527
Summary: | Chromium crashes seemingly trying to access the TPM | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Peter Robinson <pbrobinson> |
Component: | chromium | Assignee: | Tom "spot" Callaway <spotrh> |
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 34 | CC: | pkliczew, spotrh, tpopela, yaneti |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-03-25 15:02:37 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
Peter Robinson
2021-03-22 10:30:07 UTC
Also first time I've run Chromium post upgrade to F-34. I have just updated chromium 89.0.4389.82-1 (in chromium update) on fedora32 and it is crashing in the same way: Received signal 11 SEGV_MAPERR 000000000054 #0 0x561d99fd1529 base::debug::CollectStackTrace() #1 0x561d99f34986 base::debug::StackTrace::StackTrace() #2 0x561d99fd0f69 base::debug::(anonymous namespace)::StackDumpSignalHandler() #3 0x7fc17b243a90 (/usr/lib64/libpthread-2.31.so+0x14a8f) #4 0x7fc17950f285 __strlen_avx2 #5 0x561d9c8b0eca cast_channel::KeepAliveHandler::HandleMessage() #6 0x561d9c8b06ac cast_channel::KeepAliveDelegate::OnMessage() #7 0x561d9c8afa4c cast_channel::CastTransportImpl::DoReadCallback() #8 0x561d9c8afe5f cast_channel::CastTransportImpl::OnReadResult() #9 0x561d9c8b1c5e cast_channel::MojoDataPump::ReceiveMore() #10 0x561d9a8e192d mojo::SimpleWatcher::OnHandleReady() #11 0x561d99f95f72 base::TaskAnnotator::RunTask() #12 0x561d99fab12b base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl() #13 0x561d99fabe16 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork() #14 0x561d99ffb5a1 base::MessagePumpLibevent::Run() #15 0x561d99faa410 base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run() #16 0x561d99f7856c base::RunLoop::Run() #17 0x561d97d56c4a content::BrowserProcessSubThread::IOThreadRun() #18 0x561d99fbbdb8 base::Thread::ThreadMain() #19 0x561d99fe41e6 base::(anonymous namespace)::ThreadFunc() #20 0x7fc17b238432 start_thread #21 0x7fc1794ae6d3 __GI___clone r8: 0000000000000000 r9: 0000000000000000 r10: 00007fffc51f8080 r11: 00007fffc51f8090 r12: 00002e9c38590810 r13: 0000000000000054 r14: 00007fc165944fd0 r15: 00007fc165945238 di: 0000000000000054 si: 0000561da1079387 bp: 00007fc165944d60 bx: 00002e9c36cf2500 dx: 0000000000000054 ax: 0000000000000100 cx: 0000000000000014 sp: 00007fc165944d28 ip: 00007fc17950f285 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 bug has been marked as a duplicate of bug 1938962 *** |