bertd2

I can confirm that running Chromium as a snap fixes the issue. Considering that Chromium has a long history of tripping over GPU related issues on Linux, and that the issue is new in Chromium 79, I'm loath to put the blame solely on ESET here. Oh, and seeing that there seems to be no apparmor protection for Chromium, your system security is likely to increase by running Chromium as a snap anyway.