Chrome 79 always starts a core dump and crashes

[cniederr 0]

Since the last update of the chrome browser to version 79.0.3945.79 it always starts a core dump after a few seconds and crashes. If i deinstall eset NOD32 Antivirus for Linux i have no entries in the syslog and chrome works as expected. If i install the ESET NOD32 Antivirus for Linux (64bit) Chrome browser crashes. 

With the old version (cHrome 78) all works fine! Also a complete reinstall of the operating system (linux mint 19.2 - 64bit), do all updates, install browser first (at this momemt the brwoser works perfect) and finally install ESET Node32 Antivirus (64bit) for linux the problem with google chrome browser starts again, it starts a core dump and crashes.

 

Br
Christoph

 

 

[Marcos 5,273]

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.

[Nightowl 206]

Try Chromium , It works fine here with NOD32 , but I've checked the version , the latest one for it is 78 , I don't know if things will change when 79 come

[Darren 0]

I have the same issue, the companies mandated Nod32 installed and Chrome 79 crashes within a few minutes of startup.

Chromium did work, until it updated yesterday from 78 to 79, but I've downgraded Chromium to 78 to continue working.

[Marcos 5,273]

Do you have AppArmor turned on? Does disabling it make a difference?

[cniederr 0]

57 minutes ago, Marcos said:

Do you have AppArmor turned on? Does disabling it make a difference?

No, makes no difference. Same issue

Edited December 18, 2019 by cniederr

[PatrickH 0]

Same problem here - updated to the current (79.0.3945.88) Chrome on Fedora 31 this morning, and it consistently dumps core after a few seconds. If I stop the esets daemon, Chrome runs perfectly.

[tg912 0]

The same issue,Chrome 79.0.3945.88.

[Darren 0]

I've tried a couple of exclusions, the binary and also the ~/.config/google-chrome folder (which wouldn't be a permanent solution) but neither seemed to help.

[Guillaume Gautreau 0]

Same problem with me on Ubuntu 18.04 with the latest versions of Chrome, Chromium and Brave.

I tried to

• install the last version of ESET NOD32,
• Disable the realtime protection of ESET

But I'm still experiencing the same issue.

 

 

[Nightowl 206]

It does run fine with me , weird

[Steelskin 2]

Here is the output of chrome when Esset is running, each crash causes a flash from the browser window. As mentioned, if you kill all esset processes chrome does not produce any of these errors. Perhaps eset is restricting access to some of the mentioned files ?

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc

child_process_sandbox_support_impl_linux.cc

google-chrome
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:48:49-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: 3d06fa8f5af5eccd

    0K                                                         516K=0s

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:49:23-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: 5f55aaeec16904a0

    0K                                                         701K=0s

[3430:1:1229/164931.173442:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[3430:1:1229/164931.174160:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:49:34-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... [3430:7:1229/164934.169052:ERROR:command_buffer_proxy_impl.cc(124)] ContextResult::kTransientFailure: Failed to send GpuChannelMsg_CreateCommandBuffer.
200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: 5ed3418cc240f454

    0K                                                         530K=0s

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:49:46-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: 422b1aaff8efaf04

    0K                                                         608K=0s

2019-12-29 16:49:47 (608 KB/s) - ‘/dev/fd/4’ saved [16]

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:50:03-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’


    0K Crash dump id:   cb0f23b71c235577  
                                                    752K=0s

2019-12-29 16:50:04 (752 KB/s) - ‘/dev/fd/4’ saved [16]

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:50:30-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
[3548:3548:1229/165030.059220:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: f435d6b86734c2ff

    0K                                                         525K=0s

2019-12-29 16:50:30 (525 KB/s) - ‘/dev/fd/4’ saved [16]

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:50:42-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
[3600:3600:1229/165042.882151:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: deb7fb7dd42968c9

    0K                                                         390K=0s

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
--2019-12-29 16:50:57-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
[3618:3618:1229/165057.522014:ERROR:gpu_channel_manager.cc(450)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: f0c2365749e2da02

    0K                                                       ../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:(tg)kill() failure
[3164:3181:1229/165107.283404:FATAL:gpu_data_manager_impl_private.cc(990)] The display compositor is frequently crashing. Goodbye.
--2019-12-29 16:51:07-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... --2019-12-29 16:51:07-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: 831813565f56f112

    0K                                                        1.06M=0s

200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: 979b0a24e5d28e5c
    0K
                                                        521K=0s

2019-12-29 16:51:08 (521 KB/s) - ‘/dev/fd/4’ saved [16]

--2019-12-29 16:51:08-- https://clients2.google.com/cr/report
Resolving clients2.google.com (clients2.google.com)... 172.217.169.78, 2a00:1450:4009:816::200e
Connecting to clients2.google.com (clients2.google.com)|172.217.169.78|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/plain]
Saving to: ‘/dev/fd/4’

Crash dump id: 135d2926c153fe7e

    0K                                                         506K=0s

2019-12-29 16:51:09 (506 KB/s) - ‘/dev/fd/4’ saved [16]

Illegal instruction
 

(After this Illegal instruction message the entire chrome browser crashes).

[Steelskin 2]

9 hours ago, Rami said:

It does run fine with me , weird

As you mentioned above, you were running version 78.xxx of chrome. That's why you don't see a problem. You need to be running the following versions of chrome to see this crash with eset running  ..

79.0.3945.88-1 (or earlier versions of 79.xxx)

80.0.3987.16-1

81.0.4000.3-1

Edited December 29, 2019 by Steelskin
additional info

[Nightowl 206]

19 hours ago, Steelskin said:

As you mentioned above, you were running version 78.xxx of chrome. That's why you don't see a problem. You need to be running the following versions of chrome to see this crash with eset running  ..

79.0.3945.88-1 (or earlier versions of 79.xxx)

80.0.3987.16-1

81.0.4000.3-1

It is updated for now , and no crashes , it might be because of Chromium and not Chrome

Chromium

Version 79.0.3945.79 (Official Build) Built on Ubuntu , running on Ubuntu 18.04 (64-bit)

[paolo22 0]

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.

Edited January 4, 2020 by paolo22

[\djs\ 0]

Has support been able to reproduce and is dev team working on this issue yet?  I'm getting complaints about this for Chrome 79 and also for Eclipse.

[Steelskin 2]

It's now the 6th Jan and Chrome is still crashing when the Eset_daemon is running. Does anybody know if anybody is working on this issue ?

[Marcos 5,273]

28 minutes ago, Steelskin said:

It's now the 6th Jan and Chrome is still crashing when the Eset_daemon is running. Does anybody know if anybody is working on this issue ?

In https://forum.eset.com/topic/21939-eset-nod32-google-chrome-79-crashes/ we stated that Endpoint v7 will address the issue. As for the home version of ESET NOD32 for Linux Desktop, there are currently no plans for a newer version.  If there's some news on this, we'll let you know.

[Steelskin 2]

Quote

As for the home version of ESET NOD32 for Linux Desktop, there are currently no plans for a newer version.  If there's some news on this, we'll let you know.

If there is no plan for updating ESET NOD32 for Linux Desktop then my plan will be to request ESET to refund the balance of my three year subscription on multiple licences.

[peteyt 396]

3 hours ago, Marcos said:

In https://forum.eset.com/topic/21939-eset-nod32-google-chrome-79-crashes/ we stated that Endpoint v7 will address the issue. As for the home version of ESET NOD32 for Linux Desktop, there are currently no plans for a newer version.  If there's some news on this, we'll let you know.

What causes the issue? I'm a fan of eset and don't use the linux version just wondering why if there is a bug it wouldn't be fixed in all versions

[Thomas123 0]

On 1/6/2020 at 9:32 PM, Marcos said:

As for the home version of ESET NOD32 for Linux Desktop, there are currently no plans for a newer version.  If there's some news on this, we'll let you know.

We just payed a 3 year subscription recently...

Edited January 9, 2020 by Marcos
Redacted

[8j8ia68j 0]

I'm also searching for solution to this issue - I have at work few linux instances that have exact the same problem with Chrome crashing 🤢

[Nightowl 206]

On 1/7/2020 at 2:39 AM, peteyt said:

What causes the issue? I'm a fan of eset and don't use the linux version just wondering why if there is a bug it wouldn't be fixed in all versions

ESET for Linux Desktop is legacy product , it's barely updated , only the modules.

but I have no problem with my Chromium and ESET, I wonder why.

[Vrana 0]

We have the same problem after upgrading Linux Mint to 19.3.

Vivaldi browser (using the same rednering core) is crashing as well.

Dmesg is full of the following messages:

[513715.793941] vivaldi-bin[21432]: segfault at 3b8 ip 00005626bd23e3b6 sp 00007ffce3bf7500 error 6 in vivaldi-bin[5626b902c000+72c3000]

The browser often freezes and then after several freezes it is terminated.

We use the latest version of ESET NOD32 Antivirus 4 – 4.0.93.0.

Please, could you fix it?

[Steelskin 2]

If you run Chrome from the command line while the Eset daemon is running, Chrome produces the following sandbox error.

[5012:1:0109/230249.177870:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.
[5012:1:0109/230249.178539:ERROR:child_process_sandbox_support_impl_linux.cc(79)] FontService unique font name matching request did not receive a response.

If you kill the Eset daemon 'sudo pkill esets' then you don't get the above error.