Wilders Security Forums  

Go Back   Wilders Security Forums > Official ESET Support Forum > ESET Home Users Products Forum > ESET NOD32 Antivirus
User Name
Password
Register FAQ Members List Calendar Search Today's Posts Mark Forums Read

 
 
Thread Tools Search this Thread
  #1  
Old March 7th, 2012, 01:41 PM
DJ BIS DJ BIS is offline
Regular Poster
 
Join Date: Sep 2006
Posts: 50
Thumbs down NOD32 Force-Closes Google Chrome

Call it "force-closing" or crashing, I just started using Chrome but most of the time the browser cannot fully open before NOD32 (5.0.95.0) closes it.

The only way to get around it is to disable NOD32. If I do that I can browse, and then shortly after that I enable security on NOD32 again.

There is a discussion going on here, but its way over my head:
http://code.google.com/p/chromium/is...etail?id=21715

I looked around this forum for other threads relating to this issue but found 0?

Any help is appreciated.
  #2  
Old March 7th, 2012, 02:49 PM
Marcos Marcos is offline
Eset Moderator
 
Join Date: Nov 2002
Posts: 14,185
Default Re: NOD32 Force-Closes Google Chrome

They mentioned NOD32 v2 which is not supported any more and updates for v2 are going to be discontinued completely within a few months.

However, you wrote that you have v. 5.0.95 installed. Which of the modules did you need to disable in order for the browser to stop crashing? Was it HIPS, Self-defense, Real-time protection, Web access protection or HTTP scanning in the advanced setup?
  #3  
Old March 8th, 2012, 02:59 PM
DJ BIS DJ BIS is offline
Regular Poster
 
Join Date: Sep 2006
Posts: 50
Default Re: NOD32 Force-Closes Google Chrome

I simply use the "Temporarily Disable Protection" option that is available from the taskbar icon. I thought that stopped all of NOD's functions?
  #4  
Old March 9th, 2012, 12:09 AM
Marcos Marcos is offline
Eset Moderator
 
Join Date: Nov 2002
Posts: 14,185
Default Re: NOD32 Force-Closes Google Chrome

Quote:
Originally Posted by DJ BIS
I simply use the "Temporarily Disable Protection" option that is available from the taskbar icon. I thought that stopped all of NOD's functions?
That would only disable scanning but all features remain active. Do you have Chrome set to open a blank page or a specific one upon the launch?
  #5  
Old March 9th, 2012, 06:15 AM
DJ BIS DJ BIS is offline
Regular Poster
 
Join Date: Sep 2006
Posts: 50
Default Re: NOD32 Force-Closes Google Chrome

My homepage is www.google.com/ig
Sometimes it stays open for a couple of minutes but crashes quickly.
Most of the time it crashes as soon as it finishes loading the page, sometimes before it even queries for the homepage URL.
  #6  
Old March 9th, 2012, 06:27 AM
Marcos Marcos is offline
Eset Moderator
 
Join Date: Nov 2002
Posts: 14,185
Default Re: NOD32 Force-Closes Google Chrome

Please check the system Event log for possible records from the crash.
  #7  
Old March 14th, 2012, 02:56 AM
Furumori Furumori is offline
Infrequent Poster
 
Join Date: Mar 2012
Posts: 4
Default Re: NOD32 Force-Closes Google Chrome

I have the exact same issue. Nod32 5.0.95 & Chrome 17.0.963.79m.

Would often force exit/close without any error or warning message. Windows Event log shows nothing. I notice often when I try to load a webpage with flash or PDF it tends to force exit, but not always. Sometimes visiting a random website would cause it exit suddenly.

Only recently in the last few weeks has this started happening. Anyone know of a work around other than disabling nod32?
  #8  
Old March 16th, 2012, 04:24 PM
Coccinelle's Avatar
Coccinelle Coccinelle is offline
Frequent Poster
 
Join Date: Jan 2011
Location: France
Posts: 209
Default Re: NOD32 Force-Closes Google Chrome

I has the same. Google Chrome crache on Windows 7x64 bit + Resizinng GUI and "Eset need your attention"
.....so 3 buggs from september.
  #9  
Old March 26th, 2012, 10:19 AM
JohnMult's Avatar
JohnMult JohnMult is offline
Infrequent Poster
 
Join Date: Mar 2012
Posts: 42
Default Re: NOD32 Force-Closes Google Chrome

Had the same problem until yesterday. Unistall NOD32 and install Comodo Internet Security Premium. For two days now no crash at all.
After seven days almost convinced that it was Nod32 fault for Chrome and for the external drive failure...

Last edited by JohnMult : March 29th, 2012 at 08:26 AM.
  #10  
Old May 22nd, 2012, 09:55 AM
Furumori Furumori is offline
Infrequent Poster
 
Join Date: Mar 2012
Posts: 4
Default Re: NOD32 Force-Closes Google Chrome

Quote:
Originally Posted by Furumori
I have the exact same issue. Nod32 5.0.95 & Chrome 17.0.963.79m.

Would often force exit/close without any error or warning message. Windows Event log shows nothing. I notice often when I try to load a webpage with flash or PDF it tends to force exit, but not always. Sometimes visiting a random website would cause it exit suddenly.

Only recently in the last few weeks has this started happening. Anyone know of a work around other than disabling nod32?

just to update, this issue has been resolved with an eset update. info
 

Wilders Security Forums > Official ESET Support Forum > ESET Home Users Products Forum > ESET NOD32 Antivirus « Previous Thread | Next Thread »

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Settings
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -4. The time now is 11:47 AM.


Powered by vBulletin® Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2013, Wilders Security Forums