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 1774222 - Google chrome crashes after glibc update
Summary: Google chrome crashes after glibc update
Keywords:
Status: CLOSED DUPLICATE of bug 1773289
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Carlos O'Donell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-19 20:05 UTC by Valdis Kletnieks
Modified: 2019-11-19 20:08 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-19 20:08:41 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.