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: