Bug 1774222

Summary: Google chrome crashes after glibc update
Product: [Fedora] Fedora Reporter: Valdis Kletnieks <valdis.kletnieks>
Component: glibcAssignee: Carlos O'Donell <codonell>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: aoliva, arjun.is, codonell, dj, fweimer, law, mfabian, pfrankli, rth, siddhesh
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: 2019-11-19 20:08:41 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 Valdis Kletnieks 2019-11-19 20:05:34 UTC 
Description of problem:
After upgrading from  glibc-2.30.9000-17.fc32.x86_64 to glibc-2.30.9000-18.fc32.x86_64, I see massive instability in google-chrome-unstable-80.0.3964.0-1.x86_64. Tabs crashing all over the place with inscrutable "Something went wrong", extensions reporting crashes, and so on - often crashing again within seconds after I hit reload.

Reverting back to the -17 glibc and chrome becomes rock solid stable again.

There's an outside chance that this is a dup of bug #1773912/#1771946, but I'm not seeing the associated seccomp messages from #1771946 (and I *am* seeing other things from other processes in /var/audit/audit.log, so auditing and logging are in fact working)

Version-Release number of selected component (if applicable):
glibc-2.30.9000-18.fc32.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Florian Weimer 2019-11-19 20:08:41 UTC 

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