> -----Original Message-----
> From: Stefan Hett [mailto:stefan_at_egosoft.com]
> Sent: vrijdag 27 november 2015 13:47
> To: dev_at_subversion.apache.org
> Cc: users <users_at_tortoisesvn.tigris.org>
> Subject: Re: svn cleanup error "svn: E720032: Can't remove '...\.svn\tmp\svn-
> On 11/27/2015 12:16 PM, Marc Strapetz wrote:
> > One of our users is reporting frequent clean up errors:
> > svn: E720032: Can't remove
> > 'C:\Project\Path\To\WorkingCopy\.svn\tmp\svn-30D0973'
> > svn: E720032: Can't remove file
> > 'C:\Project\Path\To\WorkingCopy\.svn\tmp\svn-30D0973': Det går inte
> > att komma åt filen eftersom den används av en annan process.
> First of all: Wrong mailing list. Should go to
> users_at_subversion.apache.org (pls reply there).
> Which SVN version is being used (client / server)?
> Did you check this on the SmartSVN Forums, since you suggest it's a
> smartSVN-related issue?
> Did you consider a virus scanner issue (aka: a VS keeping the reference
> and preventing SmartSVN to release it)?
I think Marc is one of the SmartSVN developers....
Usually tempfiles are kept alive by apr pools, in which the original file handle was allocated.
And in case of JavaHL these would be kept alive by java objects... So I guess some explicit dispose/release/close call is missing somewhere.
Once the pool is properly cleaned out/destroyed most likely the files will also be deleted, as that is an operation we commonly delay to pool cleanup.
Received on 2015-11-27 14:48:43 CET