From: Marek Mrva <mrva@eof-studios.com>
To: git@vger.kernel.org
Subject: [bug] Stashes lost after out-of-memory situation
Date: Fri, 23 Oct 2020 16:53:01 +0200 [thread overview]
Message-ID: <65a3061a-47ef-9ca6-2468-5449cfc5b37c@eof-studios.com> (raw)
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
next reply other threads:[~2020-10-23 15:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 14:53 Marek Mrva [this message]
2020-10-24 17:06 ` [bug] Stashes lost after out-of-memory situation René Scharfe
2020-10-25 12:27 ` Thomas Braun
2020-10-25 15:42 ` René Scharfe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=65a3061a-47ef-9ca6-2468-5449cfc5b37c@eof-studios.com \
--to=mrva@eof-studios.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).