Google Chrome 79 crashing on Linux with NOD32 installed, ESET denies responsibility
Google Chrome and crashing, they go hand in hand! Aw, Snap! error might have hampered your way to doing something important multiple times. With Chrome 78, it expanded massively that users filled the support forum with hundreds of concerns.
In case you are not aware, the acknowledgement already came out from Mountain View. And, they found out that multiple antivirus applications are raising incompatibility issues on version 78. Moreover, the company is working in collaboration with those software vendors to make things right.
The affected users anticipated the bug would have disappeared from the next build. But no, it didn’t! Later on, the officials edited the thread on Google forum to include the M79 too. For some, disabling their security application has done the trick.
As you can see in the image given above, it has upset Linux users as well. One would think it is the same issue and disabling the real-time protection of the security software might clear the air. Interestingly, most of the concerned users have NOD32 installed.
Here comes the interesting part. Despite turning off the protection, people could see Google Chrome crashing over and over again. Have a look at the similar concern coming from an Ubuntu user (another one here).
For me disabling ESET real time protection does not help.
After starting Chrome blinks several randomly in time. If I do not do anything at opened page (even do not scroll) there no segmentation faults.
But once I scroll content, going to top of page after some time browser crash. Sometimes it crash after switching from another app to it (causing re-render it).
Ubuntu 18.04.3 LTS
NVidia drivers 390.116 (max version for my old GPU) installed without DKMS and signing module.
Chrome 79.0.3945.88 (64 bit)
One of the devastated users has taken his concern to the official ESET forum. Going by the result from his experiments, it is almost clear that NOD32 is causing issues with the browser. Have a look at it below.
Wait, the melodrama isn’t over! On the same ESET forum, we did find a post from the administrators, denying their involvement in the recent turn of events that led to crashing Google Chrome on Linux iterations.
It’s weird since ESET NOD32 Antivirus for Linux desktop does not affect browsers at all. I’d suggest collecting logs as per the KB https://support.eset.com/en/run-the-info-getcommand-on-a-linux-virtual-machine-and-send-the-logs-to-eset-technical-support and supplying logs to customer care for perusal.
Note:- Stay tuned to this story to know when we get our hands on a workaround.
PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.