Existing issues matching what you're seeing
Git for Windows version
git version 2.56.0.windows.1
cpu: x86_64
built from commit: 49d759b698127791a5f3f2759c69b983846711dd
sizeof-long: 4
sizeof-size_t: 8
shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
rust: disabled
feature: fsmonitor--daemon
gettext: enabled
libcurl: 8.22.0
OpenSSL: OpenSSL 3.5.8 25 Aug 2026
zlib: 1.3.2
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1
Windows version
Windows 11
Windows CPU architecture
x86_64 (64-bit)
Additional Windows version information
Microsoft Windows [Version 10.0.26100.9457]
Options set during installation
Editor Option: VIM
Custom Editor Path:
Default Branch Option:
Path Option: Cmd
SSH Option: OpenSSH
Tortoise Option: false
CURL Option: WinSSL
CRLF Option: CRLFAlways
Bash Terminal Option: MinTTY
Git Pull Behavior Option: Merge
Use Credential Manager: Enabled
Performance Tweaks FSCache: Enabled
Enable Symlinks: Disabled
Enable FSMonitor: Disabled
Other interesting things
According to Google AI, the most likely cause of this issue is that Git for Windows version 2.56.0.windows.1 was accidentally bundled with a debug version of libcurl-4.dll, rather than a production version. A text search of the raw binary data of libcurl-4.dll showed that it contained references to "curl_dbg_*" functions (e.g., curl_dbg_free, curl_dbg_malloc, etc.), which (Google claims) can only happen in debug builds.
Terminal/shell
PowerShell
Commands that trigger the issue
git push origin HEAD:myBranch
Expected behaviour
The commit(s) should be pushed to the remote repo successfully.
Actual behaviour
The command produces the following error message:
Assertion failed: wantedsize != 0, file ../../curl-8.22.0/lib/memdebug.c, line 216
Repository
No response
Existing issues matching what you're seeing
Git for Windows version
Windows version
Windows 11
Windows CPU architecture
x86_64 (64-bit)
Additional Windows version information
Options set during installation
Editor Option: VIM Custom Editor Path: Default Branch Option: Path Option: Cmd SSH Option: OpenSSH Tortoise Option: false CURL Option: WinSSL CRLF Option: CRLFAlways Bash Terminal Option: MinTTY Git Pull Behavior Option: Merge Use Credential Manager: Enabled Performance Tweaks FSCache: Enabled Enable Symlinks: Disabled Enable FSMonitor: DisabledOther interesting things
According to Google AI, the most likely cause of this issue is that Git for Windows version
2.56.0.windows.1was accidentally bundled with a debug version oflibcurl-4.dll, rather than a production version. A text search of the raw binary data oflibcurl-4.dllshowed that it contained references to "curl_dbg_*" functions (e.g.,curl_dbg_free,curl_dbg_malloc, etc.), which (Google claims) can only happen in debug builds.Terminal/shell
PowerShell
Commands that trigger the issue
Expected behaviour
The commit(s) should be pushed to the remote repo successfully.
Actual behaviour
The command produces the following error message:
Assertion failed: wantedsize != 0, file ../../curl-8.22.0/lib/memdebug.c, line 216Repository
No response