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

Re: svn log out of memory

From: Ivan Zhakov <ivan_at_visualsvn.com>
Date: Thu, 11 Aug 2016 18:51:29 +0300

On 11 August 2016 at 17:30, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> On 27 July 2016 at 14:09, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
>> 2016-07-26 16:10 GMT+03:00 Niemann, Hartmut <hartmut.niemann_at_siemens.com>:
>>>
>>> Hello!
>>> The command line client of Tortoise Subversion:
>>>
>>> D:\>svn --version
>>> svn, version 1.9.4 (r1740329)
>>>
>>> compiled Apr 24 2016, 15:40:35 on x86-microsoft-windows
>>>
>>> runs out of memory on a very long commit message:
>>>
>>> D:\>svn log ZD.itm -r3340
>>> r3340 | e09dueu0 | 2016-02-19 13:31:58 +0100 (Fr, 19 Feb 2016) | 2571 lines
>>>
>>> svn: E720008: Write error: Für diesen Befehl ist nicht genügend Speicher verfügbar.
>>>
>>> The XML output works fine:
>>>
>>> D:\>svn log ZD.itm -r3340 --xml
>>>
>>> Why does svn log fail on the text output but handles the same amount if it is XML?
>>>
>>
>> The actual error is:
>> OS 8: Not enough storage is available to process this command.
>>
>> Could you try run 'svn log' with redirected output, i.e.:
>> svn log ZD.itm -r3340 >test.txt
>>
> Looks like problem similar to SVN-1789:
> https://issues.apache.org/jira/browse/SVN-1789
>
I was able to reproduce this problem with huge svn:log on Windows
Server 2008 R2 (Win7), but it doesn't reproduce on Windows Server 2012
R2 and Windows 10. Most likely this 32KB WriteFile to console
limitation was fixed as part of conhost.exe fixes in Windows 8 and
later.

-- 
Ivan Zhakov
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3182000
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-08-11 18:54:19 CEST

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

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