Java Slowdowns...

We run a Java application at work and starting today (Jan 16), version 3 (build 621) of NOD32 has slowed the launch of any parts of the interface to a crawl. Current def. version is 2798.

At first I thought it could be related to the latest Java JRE 6 Update 4 so I rolled back to Java 6 Update 3. No difference. Advanced heuristics and Run-time packers are off in real-time (but on for new or modified files.)

The only way things are normal is with real-time protection totally off.

**EDIT**
Did a bit more checking. If I leave real-time protection on but uncheck the "Scan on File open" option, Java runs normally.

I have no Java issues with NOD32 installed that I could identify clearly with NOD, BUT i have them if I uninstall NOD32 v3 (even if I install 2.7).

So, the only way to run Java in Firefox is to keep NOD32 v3 installed. It never happened before with 2.7 but now it keeps crashing.
I understand this is completely weird but maybe can have advice how to uninstall all 3.0 drivers completely?

Could you please provide step-by-step instructions as how to replicate the problem? Most likely it has nothing with virus definitions.

Click to expand...

I'm not sure what I can give as far as step-by-step. The program we run is a true Java client/server application, not just the plug-in most of us see with Firefox or Internet Explorer. Whenever Java is started or ran, it can take up to 30 seconds or more before the requested action takes place. This has happened on ALL 3 PCs I have tested version 3 of NOD32. However, if I roll back to version 2.7, the additional time goes back to normal (2 or 3 seconds.)

As I noted above in post 1, the slowdown appears to have something to do with the "Scan on file open" option. (As noted in post 3, if I exclude all Java related files from the real-time scanner, all is normal then too. But since this leaves all Java files unprotected, this is obviously not the answer.)

The reason I am speculating that it may have something to do with definitions is that this problem did not exist until January 16th. I have been running version 3 since the day it was released on one PC and had no issues until then. And it is not a particular PC issue as the same problem exists on all 3 PCs that have version 3 on them. So, clearly, something changed in how version 3 of NOD32 interacts with Java on January 16th (or an update overnight the 15th?)

Based on the suggestion of a fellow member (thanks! ), I spent several hours of testing, trying to nail this down. It appears that my problems were due to a corrupt installation on the original PC. And because of my use of an exported profile (from that original PC) to the other 2 PCs that I was testing version 3 on, the other 2 PCs also exhibited the same problems.

Once I fully removed version 3 from the original PC and then reinstalled, it appeared to have "fixed" things and has been running normally. Which means, at this point, I have not yet seen any Java related slowdowns. (I exported my settings to one of the other PCs and it too is now ok with Java.)

I will monitor the situation further and report back with more info as I discover it...