libgit2 / libgit2/libgit2sharp
Crash after UnitTest with git2-15e1193.DLL with Visual Studio vstest.executionengine.exe on Windows Server 2016
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.5k
- Forks
- 925
- PR merge metrics
- No merged PRs in 30d
Description
We ran into the following error when calling git2-15e1193.DLL from libgi2sharp.dll on Windows Server 2016. The issues to not occur on Windows Server 2012 R2.
The error:
Unhandled exception at 0x00007FFA745E3882 (git2-15e1193.DLL) in vstest.executionengine.exe.7648.dmp: 0xC0000005: Access violation reading location 0x000000000000000C.
If there is a handler for this exception, the program may be safely continued.
Call Stack:
05fef9d4 67500f10 67460000 00000003 00000000 git2_15e1193!git_libgit2_shutdown+0x11c
05fefa14 67500e97 67460000 00000003 00000000 git2_15e1193!git_smart_subtransport_http+0x1ad00
05fefa28 77b5e58e 67460000 00000003 00000000 git2_15e1193!git_smart_subtransport_http+0x1ac87
05fefa48 77b30e46 67500e7b 67460000 00000003 ntdll!LdrxCallInitRoutine+0x16
05fefa98 77b30c70 00000003 00000000 b41f0c8b ntdll!LdrpCallInitRoutine+0x43
05fefb98 77b51a1c 73c248e0 73c248e0 04b89d98 ntdll!LdrShutdownThread+0x1b0
05fefc6c 754962cb 00000000 754962a0 9ffad2a9 ntdll!RtlExitUserThread+0x4c
05fefc80 77b50fd9 04b89d98 b41f0bdb 00000000 kernel32!BaseThreadInitThunk+0x2b
05fefcc8 77b50fa4 ffffffff 77b72f0e 00000000 ntdll!__RtlUserThreadStart+0x2f
05fefcd8 00000000 73c248e0 04b89d98 00000000 ntdll!_RtlUserThreadStart+0x1b
The same Error reported also to LibGit2:
https://github.com/libgit2/libgit2.github.com/issues/78
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the crash when libgit2sharp.dll calls git2-15e1193.DLL under vstest.executionengine.exe on Windows Server 2016, comparing with Windows Server 2012 R2. Inspect the git_libgit2_shutdown entry in the provided call stack and review the linked libgit2 report. Done means the shutdown-time access violation is explained and no longer occurs in the affected environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100