From: Oleksandr Gavenko <gavenkoa@gmail.com>
To: cygwin@cygwin.com
Subject: Emacs-w32 28.1-2 (marked as test) fails with: "Doing vfork: Resource temporarily unavailable"
Date: Sun, 17 Jul 2022 14:08:14 +0300 [thread overview]
Message-ID: <CAFNJpnjioj1WBWTUT=fC=V1XOi7DNLq-8REgJJvT7PnJVH53QA@mail.gmail.com> (raw)
I saw a new version of emacs-w32 28.1-2 (has 28.1-1) and gave it a try.
If has a problem with forking processes:
Doing vfork: Resource temporarily unavailable
If I switch to 28.1-1 the problem disappears. When I go back to 28.1-2
it reappears 100%.
I did "rebaseall".
I have Sophos antivir (corporate requirement)
Hope feedback gives a hint that something is wrong with the -2 update to Emacs.
TL;DR
Sometime I can capture elisp stacktrace:
Debugger entered--Lisp error: (file-error "Doing vfork" "Resource
temporarily unavailable")
make-process(:name "Compiling:
/usr/share/emacs/28.1/lisp/org/org-capt..." :buffer #<buffer
*Async-native-compile-log*> :command ("/usr/bin/emacs-w32" "--batch"
"-l" "/tmp/emacs-async-comp-org-capture.el-24hS5Q.el") :sentinel
#f(compiled-function (process event) #<bytecode -0x2abad2f059c5840>)
:noquery t)
comp-run-async-workers()
native--compile-async("/usr/share/emacs/28.1/lisp/org/org-capture.el.gz"
nil late)
defalias(org-capture-upgrade-templates #f(compiled-function
(templates) "Update the template list to the new format.\nTEMPLATES is
a template list, as in `org-capture-templates'. The\nnew format
unifies all the date/week tree targets into one that\nalso allows for
an optional outline path to specify a target." #<bytecode
-0x8c8b5d2a7dcd14c>))
require(org-capture nil t)
load-with-code-conversion("/home/user/.emacs.d/.emacs-my"
"/home/user/.emacs.d/.emacs-my" t nil)
load("~/.emacs.d/.emacs-my" t)
load-with-code-conversion("/home/user/.emacs.d/init.el"
"/home/user/.emacs.d/init.el" t t)
load("/home/user/.emacs.d/init" noerror nomessage)
startup--load-user-init-file(#f(compiled-function () #<bytecode
-0xb22ac02d4a1b12c>) #f(compiled-function () #<bytecode
-0x1f3c686ddc0c5cb5>) t)
command-line()
normal-top-level()
next reply other threads:[~2022-07-17 11:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 11:08 Oleksandr Gavenko [this message]
2022-07-17 14:15 ` Ken Brown
2022-07-17 16:35 ` Brian Inglis
2022-07-17 21:20 ` Ken Brown
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFNJpnjioj1WBWTUT=fC=V1XOi7DNLq-8REgJJvT7PnJVH53QA@mail.gmail.com' \
--to=gavenkoa@gmail.com \
--cc=cygwin@cygwin.com \
/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.
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).