Hi, I got into the same issue with Google Chrome 79 and Eset for Linux 4.0.93.0
Starting Chrome with --no-sandbox inline option fixes the issue. You get a warning by Chrome that disabling sandboxing may reduce stability and security, so this is not a permanent solution.
So the issue seems related to some incompatibility/conflict between Chrome sandboxing and Eset antivirus.