hint: Waiting for your editor to close the file... 0 [main] vim 7372 C:\Program Files\Git\usr\bin\vim.exe: *** fatal error - cmalloc would have returned NULL 334 [main] vim 7372 cygwin_exception::open_stackdumpfile: Dumping stack trace to vim.exe.stackdump Aborting commit due to empty commit message.
Note : closed all related file to the one I want to commit.
I am running git commit -a
to commit all changes I did on my project. I did the hint that the cmd offer but I still get error.
How to fix above error.
Update
When I first run the same command I was directed to a vim and I added the comment there. This time it does go to that screen just giving the error.
Running git status
gives me:
This error message can be seen in CMD wrapper like cmder.
It was recently fixed in Git for Windows 356 and PR 29.
It will be in Git 2.19 (for Windows) around Sept. 9th.
As the OP guradio comments:
Just used VScode and now I can update Git.
I got cmalloc would have returned NULL
when trying to launch vim from a command line in git bash through ConsoleZ. According to https://cygwin.com/ml/cygwin/2014-07/msg00185.html, this can happen if you set your console/terminal buffer too large. I had mine set at 5000 lines. Reducing it to 2000 resolved my issue. Hope this helps someone!
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With