Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 14 replies
  • Subscribers 6 subscribers
  • Views 6556 views
  • Users 0 members are here
Options
Suggested
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

Vuze stalls on startup thanks to Intercheck process

imom

I finally figured out why Vuze always takes several minutes to start up. When I start it, the Intercheck process jumps to 100% CPU usage for several minutes and the program stalls. If I force quit this process, Vuze starts immediately. Is there any way to stop this from happening? Vuze is he only affected application.

:1007297


This thread was automatically locked due to age.
Parents
  • 0

    The items causing the slowdown are not in Vuze.app, but in your related Vuze folders.

    What I'd suggest is disabling On-Access for the Vuze Application Support folder, and setting Vuze up to have a staging downloads folder that is also excluded.  When the torrents are complete, set them to be moved to a regular folder, and they will be scanned by on-access at that point.  This way, you don't have all the file handle open/close issues that trigger and re-trigger on-access scanning, but all downloaded content is still scanned prior to being made available.  Name the staging folder with a "." at the beginning to make it invisible in the finder if you'd like, to prevent accidental messing with folder contents.  To secure it further, you can place the folder somewhere that doesn't have executable permissions, to prevent the unlikely case that some other malicious process drops a file in there and attempts to run it.

    :1007331
Reply
  • 0

    The items causing the slowdown are not in Vuze.app, but in your related Vuze folders.

    What I'd suggest is disabling On-Access for the Vuze Application Support folder, and setting Vuze up to have a staging downloads folder that is also excluded.  When the torrents are complete, set them to be moved to a regular folder, and they will be scanned by on-access at that point.  This way, you don't have all the file handle open/close issues that trigger and re-trigger on-access scanning, but all downloaded content is still scanned prior to being made available.  Name the staging folder with a "." at the beginning to make it invisible in the finder if you'd like, to prevent accidental messing with folder contents.  To secure it further, you can place the folder somewhere that doesn't have executable permissions, to prevent the unlikely case that some other malicious process drops a file in there and attempts to run it.

    :1007331
Children
No Data