git svn seems to be broken in 2.6.3

[Dominik Rauch]

When "git svn fetch"-ing a repository with Git 2.6.3, git svn fails at a specific commit (huge, in terms of number of files) with an access violation. Unfortunately, I don't have time to analyze it further, however, it looks like the bug is new: running "git svn fetch" with Git 2.5.0 works perfectly.

Here are the contents of the perl.exe.stackdump file:

Exception: STATUS_ACCESS_VIOLATION at rip=0048360C10C

rax=0000000601E54328 rbx=000000005219E248 rcx=000000060003B1C0

rdx=0000000000000000 rsi=000000000000B256 rdi=0000000000000004

r8 =0000000000000000 r9 =0000000000000000 r10=0000000000240000

r11=000000048D78607A r12=0000000000000003 r13=000006FFFFFA92C8

r14=0000000601E1F8D0 r15=000006FFFFFA92E0

rbp=00000000000592B8 rsp=000000000023B830

program=C:\Program Files\Git\usr\bin\perl.exe, pid 14736, thread main

cs=0033 ds=002B es=002B fs=0053 gs=002B ss=002B

I hope this is the correct place to report that bug, if not, please give me a hint where I should post the issue.

Best regards,

D.R.

[Johannes Schindelin]

Hi Dominik,

please follow the suggestions at
https://git-for-windows.github.io/#contribute (you reached the wrong
mailing list, and it is recommended to open tickets at the GitHub tracker
for bugs anyway).

On Wed, 25 Nov 2015, Dominik Rauch wrote:

> When "git svn fetch"-ing a repository with Git 2.6.3, git svn fails at a
> specific commit (huge, in terms of number of files) with an access
> violation. Unfortunately, I don't have time to analyze it further,
> however, it looks like the bug is new: running "git svn fetch" with Git
> 2.5.0 works perfectly.

First of all: you might want to describe your setup in more detail, e.g.
whether you installed the 32-bit or the 64-bit version of Git for Windows.

Please note also that it is quite frustrating to read about a problem and
then get nothing concrete enough to reproduce. "huge, in terms of number
of files" might be easy to write in an email, but it is really, really
hard and tedious to get to a reproducer on any reader's side.

Further, I suspect that the problem is not a regression between 2.5.0 and
2.6.3 per se, but simply a matter of more memory congestion caused by
larger memory consumption of all involved processes.

And lastly, I think that this might be the same issue as was reported here
already:

https://github.com/git-for-windows/git/issues/274

Ciao,
Johannes

[Konstantin Khomoutov]

Well, the new preferred venue for reporting bugs is [1].

Please also note that this mailing list is dormant as it was dedicated
to the development of GfW up to 1.9.x. Since the project transitioned
to the new development foundation and was rebranded "Git for Windows",
it got the new mailing list which is [2].

1. https://github.com/git-for-windows/git/issues
2. https://groups.google.com/forum/#!forum/git-for-windows