From: Marek Mrva Date: Fri, 23 Oct 2020 14:53:01 GMT Subject: [bug] Stashes lost after out-of-memory situation Message-ID: <65a3061a-47ef-9ca6-2468-5449cfc5b37c@eof-studios.com> Hello, hopefully this is the correct mailing list - apologies if it is not. After issuing "git stash pop" while being low on memory, the following was printed to the console: 0 [main] git 2061 fhandler_disk_file::fixup_mmap_after_fork: requested 0x6FFFC1550000 != 0x0 mem alloc base 0x0, state 0x10000, size 17545957736448, Win32 error 1455 36836 [main] git 2061 C:\cygwin64\bin\git.exe: *** fatal error in forked process - recreate_mmaps_after_fork_failed 37523 [main] git 2061 cygwin_exception::open_stackdumpfile: Dumping stack trace to git.exe.stackdump 0 [main] git 2056 dofork: child -1 - forked process 12100 died unexpectedly, retry 0, exit code 0x100, errno 11 error: cannot fork() for status: Resource temporarily unavailable Dropped refs/stash@{0} (06d44ccc5ed2ac93b370100f481147ae4f0065db) error: cannot fork() for rev-parse: Resource temporarily unavailable Afterwards, the result of "git stash list" is empty, even though there used to be more than 10+ stashes saved. Obviously while being low on memory, one should not expect commands to run properly. Losing all the *other* stashes could hopefully be somehow avoided, if possible. It is worth mentioning this happened in a cygwin environment on Windows. Any help would be greatly appreciated! :) With best regards, Marek Mrva