You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Wolgang Kießling <in...@wolfgang-kiessling.de> on 2009/04/14 06:28:45 UTC
memory leak
commit test:
files filesize usedRAM RAM/files TortoiseProc.exe / svn.exe
67 134 MB 34 MB ~0,5 MB T
284 ~6 MB 142 MB ~0,5 MB T
284 ~6 MB 142 MB ~0,5 MB S
=> each file allocates a memory of 0.5 MB.
use tools:
Windows XP Prof. SP3
TortoiseSVN 1.6.0, Build 15855 - 32 Bit
svn.exe 1.6.0 (SlikSvn:tag/1.6.0@36687)
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1704451
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: Re: memory leak
Posted by Manfred Lange <ml...@agileutilities.com>.
I agree with Wolfgang. It looks like a memory leak. I have the same issue on a Windows Vista platform (32 bit) with SVN 1.6.1.
To reproduce:
1. Create a new repository for this test (can be an existing one as well)
2. Added a large number of folders and files to the repository (I use a folder that contains 13,000 files).
3. Commit the added folders and files.
4. Wait until SVN reports 'out of memory' in it's output
In my environment it takes about 1 hour. SVN consumes about 1 kByte per file during that time and the memory consumption goes up while transferring the content to the server.
The issue is reproducable with both SVN 1.6.1 and the equivalent TortoiseSVN version. The former at least reports the error properly before it closes. TortoiseSVN simply crashes.
It certainly can also be related to memory fragmentation. Without looking into the source code and based on my experience this looks more like a memory leak than fragmentation.
I've reported this issues as bug #3411 which was closed as a duplicate to bug #1964 without further investigation. Bug #1964 has been open since 2004 (if the date is correct).
Admittedly this is not a typical change set. However, I wanted to use the above approach for migrating to Subversion. I am also open to work arounds or to different approaches for getting a large number of files into a repository. The issue described above wouldn't go away with this.
My configuration:
- Windows Vista, 32 bit, all service packs / hotfixes installed
- SVN 1.6.1
- TortoiseSVN 1.6.1
Cheers,
Manfred.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2125901
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: memory leak
Posted by "Hyrum K. Wright" <hy...@mail.utexas.edu>.
On Apr 14, 2009, at 1:28 AM, Wolgang Kießling wrote:
> commit test:
>
> files filesize usedRAM RAM/files TortoiseProc.exe / svn.exe
> 67 134 MB 34 MB ~0,5 MB T
> 284 ~6 MB 142 MB ~0,5 MB T
> 284 ~6 MB 142 MB ~0,5 MB S
>
> => each file allocates a memory of 0.5 MB.
>
> use tools:
> Windows XP Prof. SP3
> TortoiseSVN 1.6.0, Build 15855 - 32 Bit
> svn.exe 1.6.0 (SlikSvn:tag/1.6.0@36687)
Although, interesting, this really doesn't give us a lot of
information to determine if there's a leak, and where it is. Do you
have a reproduction script for the command line client you could supply?
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1709418
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].