Crash with "Failed to mmap" error (using Git)

S_Mackedie

Hey guys,

Got a very annoying crash that happens regularly when dealing with source control. Error details:

Failed to mmap. No data written: Not enough storage is available to process this command.

This happens very often, more often than not when committing or even just viewing changes to commit. Even closing the Source Control tab after it's thrown the error will throw it twice more. What's more, I can't submit the error report because that crashes SSMS altogether before it even sends, so that's why I'm here now instead.

So far my only work around has been to repeatedly close and reopen the Source Control tab and hope it doesn't throw the error. Eventually it works, but it can take a number of times doing this before it's usable. Using git outside of SSMS works fine with no issues.

SQL Source Control version is 6.0.5.7062.

Sergio R

Hi,

That error can happen due to an issue with the Library that the "default" Git connection method uses.
A workaround for this is to unlink the DB and re-link using the Custom Method which provides an alternative way to connect to Git: https://documentation.red-gate.com/soc6/linking-to-source-control/other-source-control-systems/link-to-a-custom-setup

However with the Custom method you will not be able to Push/Pullor or view revision history from SSMS.

Thank you,

jimVisage1980

Are there any plans by Redgate to fix this ?

Workaround works but then you lose the functionality like seeing which branch you are on in the Redgate source control tab as well as revision history etc.