andre.s 1 Posted December 17, 2019 Share Posted December 17, 2019 The newest Google Chrome 79 crashes if ESET NOD32 is running. If I uninstall eset Google Chrome is working fine. If I install Google Chrome 78 and eset is running its also fine an no crashes. OS is Debian 9 or 10 google-chrome-stable 79.0.3945.79-1 Here is what I see on terminal if Google Chrome crashes ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [2831:135:1217/143835.660701:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer. [2854:151:1217/143837.090861:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [2854:151:1217/143849.147978:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [4334:4334:1217/144249.309433:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [4521:4521:1217/144259.214596:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [4601:4601:1217/144310.006822:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization. ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure [2489:2509:1217/144319.131218:FATAL:gpu_data_manager_impl_private.cc(990)] The display compositor is frequently crashing. Goodbye. Trace/Breakpoint ausgelöst Any hint what I can try that the newest Google Chrome is working? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted December 17, 2019 Administrators Share Posted December 17, 2019 Although ESET should not interfere with browsers on Linux in any way, if you are positive that the issue go away after uninstalling EAV I'd recommend opening a support ticket with customer care and providing them also logs collected 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. Link to comment Share on other sites More sharing options...
mausch 0 Posted December 18, 2019 Share Posted December 18, 2019 I just started seeing the same issue with Chromium 79 (and I'm also running ESET). I used to run Chromium with the --use-gl=osmesa flag because otherwise it would crash for some reason (different from the crash discussed on this topic). I now simply stopped using --use-gl=osmesa and it doesn't crash any more. Seems Chromium fixed the original rendering bug I had. Link to comment Share on other sites More sharing options...
Alexander Lemke 0 Posted December 18, 2019 Share Posted December 18, 2019 Same here. Chrome 78 & Chromium 78 + ESET = No Problems Chrome 79 & Chromium 78 + ESET = Chrome crashes (same terminal output as postet above), Chromium working Chrome 79 & Chromium 79 + ESET = Crome & Chromium crash Chrome 79 & Chromium 79 NO ESET = No Problems Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted December 18, 2019 Administrators Share Posted December 18, 2019 We have reproduced the issue and will pass it to developers for further investigation. Link to comment Share on other sites More sharing options...
Marcio 0 Posted December 19, 2019 Share Posted December 19, 2019 Same issue here! NOD32 for linux is obviously crashing chromium as well google chrome. I've just confirmed it, installing ESET software only after chromium. The same test was made with google chrome. By the way, Application Armor have to be configured to allow NOD32 works in peace. Link to comment Share on other sites More sharing options...
wokkiedokkie 0 Posted December 26, 2019 Share Posted December 26, 2019 For additional info,I would liek to share my expertience: On two different computers with Ubuntu 16.04, Chrome and Chromium version 79.x crash, with or without Nod32. Also after uninstalling and reinstalling all products and rebooting in between. On pone of these computers I have removed chrome and chromium, and installed the snap version of chromium version 79. This runs without issue, also when Nod32 ins running! On Windows 10 (10.0.14393) With Eset Internet Security 13.0.24.0 I experience no problem with Chrome 79.x. Hope this helps. Link to comment Share on other sites More sharing options...
YinYang 0 Posted December 26, 2019 Share Posted December 26, 2019 Hi any update on this topic ? I'm facing the same issue... I'd love to provide additional feedback if necessary. Chrome : Version 79.0.3945.88 ESET: 4.0.93.0 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted December 27, 2019 Administrators Share Posted December 27, 2019 The issue will be addressed in Endpoint v7 which is planned for Q1/2020. Link to comment Share on other sites More sharing options...
Ellis 0 Posted December 27, 2019 Share Posted December 27, 2019 RE "The issue will be addressed in Endpoint v7 which is planned for Q1/2020. " What does this mean for existing users like myself who are experiencing this problem. I am using Chrome : Version 79.0.3945.88 (Official Build) (64-bit) ESET NOD32 Antivirus 4 : 4.0.93.0 (2 year licence) Linux Mint 19 / Mate Will a fix be supplied or will Endpoint V7 be provided free to existing customers ? Link to comment Share on other sites More sharing options...
Steelskin 2 Posted January 6, 2020 Share Posted January 6, 2020 On 12/27/2019 at 8:01 PM, Ellis said: Will a fix be supplied or will Endpoint V7 be provided free to existing customers ? Or will we all be requesting refunds and the associated bad press that will produce ? Really ? A bug fix in Q1/2020 and no bug fix planned for the ESET Linux Desktop Home edition ? Seriously ? 😠 Link to comment Share on other sites More sharing options...
bertd2 0 Posted January 7, 2020 Share Posted January 7, 2020 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. Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted January 7, 2020 ESET Staff Share Posted January 7, 2020 Hello, ESET licenses are not version-specific. Meaning any customer using currently V4 on linux, can use any other available version on any of the platforms. V4 is a very old code-base, meaning addressing compatibility issues with newer browsers will be targeted towards the next major release of the V7 Linux Endpoint. Link to comment Share on other sites More sharing options...
Ellis 0 Posted January 7, 2020 Share Posted January 7, 2020 Thankyou. Link to comment Share on other sites More sharing options...
YinYang 0 Posted January 11, 2020 Share Posted January 11, 2020 The issue is now increase to other browsers ( Opera version : 66.0.3515.27). Do we have ETA for the Linux Release to fix the issue ? Link to comment Share on other sites More sharing options...
royi_klein_40 0 Posted January 15, 2020 Share Posted January 15, 2020 also on linux mint based on ubuntu 18. this is very sad Link to comment Share on other sites More sharing options...
Kirill 0 Posted January 20, 2020 Share Posted January 20, 2020 On 1/7/2020 at 3:04 PM, MichalJ said: the next major release of the V7 Linux Endpoint And what exactly does this mean if https://www.eset.com/int/business/endpoint-antivirus-linux/download/ still only offers to download V4? Are you saying that you've just dropped the support for Linux Desktop product that you sold with multiple year licenses? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted January 21, 2020 Administrators Share Posted January 21, 2020 The issue will be addressed both in Endpoint and NOD32 for Linux desktop. Kirill 1 Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted January 21, 2020 ESET Staff Share Posted January 21, 2020 @Kirill Licenses for ESET products are not sold for a specific product version. Meaning, that with your current license you will be eligible to use the new V7 as well. Linux Endpoint product is the last one running the old version of architecture / scanning core, and it will be updated to V7 soon. We are already running a beta program (available here), V7 should not have this issue at all. Kirill and Nightowl 2 Link to comment Share on other sites More sharing options...
Kirill 0 Posted January 21, 2020 Share Posted January 21, 2020 Great to hear that, thank you very much! Link to comment Share on other sites More sharing options...
Ellis 0 Posted February 26, 2020 Share Posted February 26, 2020 Hi, Can we get an update here. I noticed from another post that the issue is being looked at but appears so far it cannot be fixed ? Can you let us know if they are going to continue to try to resolve this ? Thanks. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted February 26, 2020 Administrators Share Posted February 26, 2020 There is no update yet on this. While the crash issue was fixed, another severe issue with detection was found. Currently we are in the process of deciding how to carry on. Link to comment Share on other sites More sharing options...
Ellis 0 Posted February 26, 2020 Share Posted February 26, 2020 Thanks Marcos. If you could lets us know what the final outcome is once a decision is made, that is whether it can be fixed or not, that would be appreciated. This will help me decide on whether I need to look for another solution elsewhere, though I would prefer to continue using and supporting Eset. Again Thanks. Link to comment Share on other sites More sharing options...
Jozef Sťaffen 0 Posted March 3, 2020 Share Posted March 3, 2020 Thank you, waiting for fix Link to comment Share on other sites More sharing options...
Administrators Marcos 5,069 Posted March 3, 2020 Administrators Share Posted March 3, 2020 A fix will be included in v4.0.95. There's no ETA yet but it shouldn't take long. Peter Randziak 1 Link to comment Share on other sites More sharing options...
Recommended Posts