Jump to content

Archived

This topic is now archived and is closed to further replies.

haywarle

Process crash

Recommended Posts

 

Who knows how many people around the world have been having this issue and don't make a mention of it. Because they're not computer savvy enough to know what's going on. Imagine the masses of people taking their Macs to genius bars, or technicians for unneeded repairs [...] This whole kernel panic issue smells like a BUG!

 

 

I'm noticing on the Apple Support Communities and other websites that other users are also having Kernel Panics with esets_proxy & esets_daemon... with this amount of people having the same issue it seems like it's a real issue for almost anyone.

 

https://discussions.apple.com/message/25474945#25474945

https://discussions.apple.com/message/25387226#25387226

hxxp://forums.whirlpool.net.au/forum-replies.cfm?t=2239792

 

Has there been any progress made since?

 

Edit; had my second Kernel Panic moments ago by esets_proxy. I was just browsing the web on Safari, no other applications installed.

Share this post


Link to post
Share on other sites

Same issue here. Installed version 6 and I began having kernal panics and crashes (the culprits were both esets_proxy and esets_daemon). I have a mid-2009 Macbook Pro running OS X 10.8.5. But the panic crashes weren't the only problem… I noticed my cooling fan was kicking in all the time and my CPU temperature was spiking between 100 and 105 centigrade (damn hot, to be sure!). I checked my Activity Monitor and found that eset_daemon was placing enormous loads on my CPU. I have since uninstalled version 6 and reinstalled 4.1.86.4 (just to be safe) and have had no problems so far. 

 

My question would be, has anyone else had the same problems with version 6 eset_daemon and high CPU loads? If so, is there a solution beyond uninstalling the application?

 

I will continue to use 4.1.86.4 until ESET resolves these issues. 

Share this post


Link to post
Share on other sites

I’ve had two kernel panics since I updated to version 6 yesterday. I should also add that yesterday I cloned my old HD to a new larger one and the panics occurred after using the new one as eset was trying to update its virus database. This last one was caused by esets_daemon so I uninstalled ESET entirely. I’m amazed that other people are finding the same problem. I should also add that esets_daemon has caused me a lot of trouble even on version 5 as it uses up a lot of my processor and causes the fans to kick up.

Share this post


Link to post
Share on other sites

I have had several kernel panics after a clean install of version 6.0.9.1.

 

I have gone back to 5.0.115.0, despite the fact that this version regularly makes my system unresponsive while browsing the Internet with Firefox. Each time I have to hard-reset my system and 'repair' my harddisk/system. In the event log I frequently get the error message "Transparent proxy - Cannot accept connection: Input/output error".

 

I am considering switching to a different virus scanner altogether if these problems keep coming back and are not resolved. An other complaint is the inability of ESET Cyber Security to scan pop3s and imaps connections.
 

Share this post


Link to post
Share on other sites

@Tese

 

I too am considering moving onto a new anti virus if these issues continue. Eset has always been great for years, but they're beginning to add too many uneeded features that other anti virus' have done in the past over time. Which if they haven't noticed will work against them in the long run. Focus on maintaining a stable AV, instead of going overboard with other features on every release. This is why this bug slipped through...

 

Still no word from Eset, the least someone can do is apologize!

Share this post


Link to post
Share on other sites

I can assure you that the issue is being seriously looked at. So far we've received less than 10 reports about this crash from individual distributors. Many other users have been using ESET CyberSecurity v6 without issues and we were unable to reproduce the crash either. We've also asked one of the largest Apple sellers to report us issues related to ECS v6 but no issue has been reported to date except an issue with starting OS X caused by cleaning specific adware about 2-3 weeks ago. However, this particular issue also affected some other AV vendors and was fixed very quickly.

 

It would really help us if you could help us determine a common pattern. Could you confirm or deny that the kernel panic always occurs while browsing websites?

Share this post


Link to post
Share on other sites

It had nothing to do with web browsing. It was always triggered by the virus update from the software and the process that triggered the panic was always esets_daemon. This process also caused me a lot of trouble in v5 because esets_daemon would run up my cpu and fan every time eset was updating.

Share this post


Link to post
Share on other sites

I presume that most users here are having an issue with kernel panic indicated by "BSD process name corresponding to current thread: esets_proxy" in $HOME/Library/Logs/DiagnosticReports/Kernel*.panic logs. This issue has been reported only with ECS v6 so far to my best knowledge.

The issue related to esets_daemon must be a different one which would need to be investigated separately. Please report it to Customer care who should subsequently provide a simple script that collects all necessary logs needed by engineers for analysis of the issue.

Share this post


Link to post
Share on other sites

I have two separate issues.

 

1. Under version 6.0.9.1 I have had two kernel panics. Both were related to the process esets_proxy. After these two events I decided to downgrade to version 5.0.115.0.

 

2. Under version 5.0.115.0 I got numerous system freezes. In which the system becomes unresponsive showing the coloured wheel spinning forever. I was always browsing the Internet with Firefox at the time of a system freeze. I cannot link these with a panic report, since it's not a kernel panic. ESET's event log however is showing a large number of error messages "Transparent proxy - Cannot accept connection: Input/output error".

 

The problem with these kernel panics and system freezes is that each time I have to hard-reset my system and 'repair' my harddisk afterwards. Which is time-consuming.

 

Keltian mentions panics while updating virus definitions. I haven't had any panics while updating, but do recognise esets_daemon taking up 100% CPU time while updating. While updating (looking for an update?) I cannot use my Mac. Everything seems to grind to a halt.

Share this post


Link to post
Share on other sites

As for the kernel panics related to esets_proxy, we assume it occurs if there's another application like a network monitor or 3rd party proxy server installed. We've seen the issue also reported by a user who had no ESET's product installed. We assume that the kernel panic might be triggered by a bug in OS X, hence we're going to contact Apple on this matter.
 

It had nothing to do with web browsing. It was always triggered by the virus update from the software and the process that triggered the panic was always esets_daemon. This process also caused me a lot of trouble in v5 because esets_daemon would run up my cpu and fan every time eset was updating.


Please contact Customer care who will provide you with a script for collecting logs for further analysis by our engineers. An issue like that has recently been identified and fixed, however, without logs it's impossible to tell if it's the same issue or not.

Share this post


Link to post
Share on other sites

As for the kernel panics related to esets_proxy, we assume it occurs if there's another application like a network monitor or 3rd party proxy server installed. We've seen the issue also reported by a user who had no ESET's product installed. We assume that the kernel panic might be triggered by a bug in OS X, hence we're going to contact Apple on this matter.

 

Just wanted to note that anything like a network monitor or proxy server was never installed on this Mac and the two kernel panics only occurred after installing Version 6, I've never had a kernel panic ever beforehand. I'm happy to hear that progress is being made however and I do hope the cause or solution is found soon. Thank you for the update!

Share this post


Link to post
Share on other sites

I haven't had a kernel panic while running on version 6, but just have problems with the esets_proxy service. The process seems to stutter and takes long time to render web pages over time to the point where the service just locks up and no longer processes data. This does not block me from viewing webpages with any web browser, but the proxy service is clearly no longer filtering data anymore.

 

I can 90% guarantee that the service will crash after waking up from sleep mode. If I manually kill the esets_proxy, it's able to revive and start processing again. It's more of an annoyance. 

Share this post


Link to post
Share on other sites

Hi,

 

after upgrading to 10.9, still with ESET 5, no problem. Panic crash/reboot started after upgrading to 6. One computer crashed when I was away, so nobody was surfing the net and the computer did not woke up (It never sleeps, as configured in system prefs). If I killed all of eset ( sudo pkill -9  eset ) the computer stopped crashing until next reboot.

 

I finally downgraded to ESET 5, and no more crash.

 

Here's one crash as recorded by the panic log: hxxp://www.lzi.ch/eset/Kernel_2014-04-21-203910_egg.panic

And here's the actual (with ESET 5) system_profile's result: hxxp://www.lzi.ch/eset/system_profiler.txt

 

HTH

 

Best regards

Share this post


Link to post
Share on other sites

Since installing version 6.0.9.1 of Cyber Security on my MacBook Pro running OS Mavericks, I have experienced 2 restarts due to Kernel Panics. Prior to installing Cyber Security I had never experienced a Kernel Panic.

 

Please advise on how to prevent further restarts. 

 

Note: I have also got a problem with running scheduled scans in that they never start. Again this problem never existed prior to Ver 6.0.9.1.

Share this post


Link to post
Share on other sites

More people are now experiencing this kernel panic issue from esets_proxy or daemon:

 

https://discussions.apple.com/message/25597554#25597554 (esets_proxy)

https://discussions.apple.com/message/25586992#25586992 (esets_proxy)

https://discussions.apple.com/message/25538931#25538931 (esets_daemon)

 

I have a feeling that users who experience the panics are unaware of how to see what caused it and is making this issue seem smaller than it already is.

Share this post


Link to post
Share on other sites

After having 3 Kernel Panics occur I went without one for about two weeks. Mind you I wasn't using my Macbook much these past two weeks. Then all of a sudden I got my 4th Kernel Panic a couple days ago. Enough is enough so last night I uninstalled Eset Cyber Security 6 using the uninstaller in the applications "Resources" folder. I then went ahead and downloaded Eset Cyber Security 5 and re-installed that version (which never gave me problems before). Let's see how this fares out... I had every Kernel Panic occur during web browsing use with version 6. I noticed web pages took a slightly bit longer to load in version 6, and the real time scanner numbers never really increased. With v5 installed again everything seems to be working fine.

 

I was going to walk away from using Eset completely... We'll see how this goes...

Share this post


Link to post
Share on other sites

 

I was going to walk away from using Eset completely... We'll see how this goes...

 

I like your candor, however not giving ESET a chance to fix or repair, would be counter-productive. ( You would end up with a less protective solution (my opinion :) )

Share this post


Link to post
Share on other sites

 

 

I was going to walk away from using Eset completely... We'll see how this goes...

 

I like your candor, however not giving ESET a chance to fix or repair, would be counter-productive. ( You would end up with a less protective solution (my opinion :) )

 

Ah, but are ESET attempting to fix the problem, do they even monitor this forum?

Share this post


Link to post
Share on other sites

From my experiece crashes were not happening while browsing the internet but while using regular tools such as Adobe Creative Suite or Microsoft Office

Share this post


Link to post
Share on other sites

Hi all,

 

MP 3.1 OS X Mavericks 10.9.2 (13C1021) after security update 2014-002 1.0

 

Reverted back to ECS Pro 5.0.115.0 and no more panic crash/hang/spin etc issues.

 

I hope ESET will release an update/bug fix soon to solve this issue and the FireWall Interactive Mode bug in v6! 

 

Regards

Share this post


Link to post
Share on other sites

Hello - same issues at work and at home on both iMacs and MacBook running 10.9.2 and ESET 6.0.9.1.  I have had three crashes today working from home all have been esets_proxy. Decided to uninstall. Need a solution soon.

 

Wed Apr 30 10:39:39 2014

Panic(CPU 5): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff80410853f8, spinlock owner: 0xffffff8040fad590, current_thread: 0xffffff8040fad590, spinlock_owner_cpu: 0x5

RAX: 0xffffff80530aab58, RBX: 0x0000000000000001, RCX: 0xffffff80530aab48, RDX: 0xffffff80530aab58

RSP: 0xffffff811ca0bec0, RBP: 0xffffff811ca0bf70, RSI: 0xffffff80530aab90, RDI: 0x0000000000000000

R8:  0x0000000000000000, R9:  0x0000000000000000, R10: 0xffffff811ca0bc10, R11: 0x0000000000000200

R12: 0x0000000000000000, R13: 0xffffff80530aab48, R14: 0xffffff80410853f0, R15: 0xffffff8041085338

RFL: 0x0000000000000286, RIP: 0xffffff802b5c403c, CS:  0x0000000000000008, SS:  0x0000000000000010

Backtrace (CPU 5), Frame : Return Address

0xffffff81141baf50 : 0xffffff802b2e1f21 

0xffffff81141baf80 : 0xffffff802b2db43f 

0xffffff81141bafd0 : 0xffffff802b2f3539 

0xffffff811ca0bf70 : 0xffffff802b5c4580 

0xffffff811ca0bfb0 : 0xffffff802b2d7047 

 

BSD process name corresponding to current thread: esets_proxy

 

Mac OS version:

13C1021

 

Wed Apr 30 12:33:55 2014

Panic(CPU 2): NMIPI for spinlock acquisition timeout, spinlock: 0xffffff80203d6340, spinlock owner: 0xffffff801e990000, current_thread: 0xffffff801e990000, spinlock_owner_cpu: 0x2

RAX: 0x0000000000000000, RBX: 0xffffff800b6d4c40, RCX: 0xffffff801e990000, RDX: 0x0000000000000000

RSP: 0xffffff80fc12be78, RBP: 0xffffff80fc12beb0, RSI: 0x0000000029a0de7b, RDI: 0xffffff801e15edd8

R8:  0x0000000000000000, R9:  0xffffff80f3fd0068, R10: 0xffffff80fc12bc10, R11: 0x0000000000000200

R12: 0x00000000fffffffe, R13: 0xffffff80237a6be8, R14: 0xffffff801e15edd8, R15: 0xffffff801e15ed00

RFL: 0x0000000000000246, RIP: 0xffffff800b0d09ee, CS:  0x0000000000000008, SS:  0x0000000000000010

Backtrace (CPU 2), Frame : Return Address

0xffffff80f3f56f50 : 0xffffff800b0e1f21 

0xffffff80f3f56f80 : 0xffffff800b0db43f 

0xffffff80f3f56fd0 : 0xffffff800b0f3539 

0xffffff80fc12beb0 : 0xffffff800b3c428b 

0xffffff80fc12bf70 : 0xffffff800b3c4580 

0xffffff80fc12bfb0 : 0xffffff800b0d7047 

 

BSD process name corresponding to current thread: esets_proxy

 

Mac OS version:

13C1021

 

Wed Apr 30 16:29:34 2014

panic(cpu 0 caller 0xffffff800dcdbe7e): Kernel trap at 0x0000000000000000, type 14=page fault, registers:

CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x00000000296c9052, CR4: 0x00000000000606e0

RAX: 0xffffff800e248360, RBX: 0x0000000000000001, RCX: 0x0000000000000020, RDX: 0x0000000000000000

RSP: 0xffffff80fee5beb8, RBP: 0xffffff80fee5bf70, RSI: 0x0000000000000000, RDI: 0xffffff80372d1098

R8:  0x0000000000000000, R9:  0xffffff80f0ad0068, R10: 0xffffff80fee5be70, R11: 0x00000000a1e8eb00

R12: 0x00000000fffffffe, R13: 0xffffff80372d1098, R14: 0xffffff8020e4cf48, R15: 0xffffff8020e4cf00

RFL: 0x0000000000010246, RIP: 0x0000000000000000, CS:  0x0000000000000008, SS:  0x0000000000000010

Fault CR2: 0x0000000000000000, Error code: 0x0000000000000010, Fault CPU: 0x0

 

Backtrace (CPU 0), Frame : Return Address

0xffffff80fee5bb40 : 0xffffff800dc22fa9 

0xffffff80fee5bbc0 : 0xffffff800dcdbe7e 

0xffffff80fee5bd90 : 0xffffff800dcf3376 

0xffffff80fee5bdb0 : 0x0 

0xffffff80fee5bf70 : 0xffffff800dfc4580 

0xffffff80fee5bfb0 : 0xffffff800dcd7047 

 

BSD process name corresponding to current thread: esets_proxy

 

Share this post


Link to post
Share on other sites

For the second time in 3 months,  I find myself uninstalling Eset again.  Add me the the list of people with the kernel panics.

 

This happen on version 5,  I didn't reinstall until version 6.  Poor QA

Share this post


Link to post
Share on other sites

Same here. I have one MAC Book Pro and one MAC AIr. In both after instaling latest update 6.9.1 i faced 3-4 crashes every day. In the past have zero crashes. 

 

I uninstalled it and all is normal now and much more faster.

 

It is ridiculous to issue an update and cause so much problems to users 

 

 

 

Share this post


Link to post
Share on other sites

Since reinstalling version 5.0.115.0 4 days since, I have not experienced any more kernel panics

Share this post


Link to post
Share on other sites

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...