[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: TortoiseSVN 1.4.0.7501 causes McAfee problem

From: Stefan Kng <tortoisesvn_at_gmail.com>
Date: 2006-09-26 21:01:54 CEST

Peter Termaten wrote:

> I'm not sure who 'owns' this problem, but the following happens after
> installing TortoiseSVN 1.4.0.7501 on WinXP/SP2
>
> When checking out a project using TortoiseSVN, Zend Platform 5.2.0/233
> starts behaving very slow. Taskmanager shows 100% CPU usage of McAfee
> Virusscanner (version 10.0.27, engine 4450 DAT 4859. After disabling the
> viruschecker things are back to normal again.
>
> Using either a network drive or local drive for checking out does not
> make a difference. Exporting instead of checking out the project does
> not cause the problem.
>
> Reinstalling TortioseSVN 1.3.5/6804 and a new checkout makes the problem
> disappear again.
>
> Looks like something in the new .svn content makes McAfee very unhappy.

Yes, version 1.4.0 has a new working copy format. 1.3.x used xml for the
working copy metadata, which I guess made McAfee just ignore those
files. But the current version uses another format (which is faster than
xml, but not quite readable text anymore). So McAfee seems to think that
these files could be dangerous and checks them much more intensive.

Sorry, but there's nothing we can do about that. I hope that McAfee has
some option to ignore certain directories from scanning? If not,
complain with McAfee.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Sep 26 21:02:04 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.