Guest User!

You are not Sophos Staff.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Slow launching java files and browser hangs.

Has anyone else seen this?

When launching pages that are Java enabled they are slow to open, may not complete and I may have to Force the browser to quit as the browser process will run at 100% plus?  This happens in Firefox and Safari (Chrome does not support the new 64 bit Java version)!  After disabling Sophos on-access scan the pages work fine and open and test in sub seconds!

However my wife’’’’s MBA does not see this problem with same code levels!

Test your Java version here.  This hangs my browsers if I have active scan.

http://www.java.com/en/download/installed.jsp

10 Month old MacBook Pro:  2.2 Ghz i7, 8GB Ram.  256GB SSDD.  – No Slouch

OS X 10.8.2 (Mountain Lion) with all updates.  Java Version 7, update 7 (Latest) and Sophos 8.0.6C.

This problem was not as noticable with JRE v6.

I have cleared out cached Java and browser files.  Run Maintenance scripts and reinstalled the OS.  No files in quarantien!

Sophos works great for me except for this hickup.  I do not notice any slow up when running active scan in general except for Java files. 

Suggestions please. 

Thanks

Graham

:1010138


This thread was automatically locked due to age.
Parents
  • Currently, if archive scanning is disabled, Sophos will still extract small java jar files, which is probably what is causing this slowdown.  There have been some changes to this code that should speed up operation of Java software, as well.  Also, it could be that there was some other memory-based leak or lock-up that was causing the issue -- as re-scanning existing files that have already been scanned and haven't been modified isn't supposed to happen in the first place.

    :1010266
Reply
  • Currently, if archive scanning is disabled, Sophos will still extract small java jar files, which is probably what is causing this slowdown.  There have been some changes to this code that should speed up operation of Java software, as well.  Also, it could be that there was some other memory-based leak or lock-up that was causing the issue -- as re-scanning existing files that have already been scanned and haven't been modified isn't supposed to happen in the first place.

    :1010266
Children
No Data