Emacs-w32 28.1-2 (marked as test) fails with: "Doing vfork: Resource temporarily unavailable"

Emacs-w32 28.1-2 (marked as test) fails with: "Doing vfork: Resource temporarily unavailable"

[Oleksandr Gavenko]

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()

Re: Emacs-w32 28.1-2 (marked as test) fails with: "Doing vfork: Resource temporarily unavailable"

[Ken Brown]

On 7/17/2022 7:08 AM, Oleksandr Gavenko wrote:
> 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

Please see the release announcement:

   https://cygwin.com/pipermail/cygwin-announce/2022-April/010529.html

Ken

Re: Emacs-w32 28.1-2 (marked as test) fails with: "Doing vfork: Resource temporarily unavailable"

[Brian Inglis]

On 2022-07-17 08:15, Ken Brown wrote:
> On 7/17/2022 7:08 AM, Oleksandr Gavenko wrote:
>> 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

> Please see the release announcement:
>    https://cygwin.com/pipermail/cygwin-announce/2022-April/010529.html

Could you not perhaps at emacs (initial) startup add the rebase userpath 
eln-cache entry, and create a shell script to rebase the eln-cache 
entries which could be e.g. ~/.emacs.d/cygwin-rebase-eln-cache or 
elsewhere, and perhaps that script could also initially add the rebase 
userpath eln-cache entry, to make life easier for users.

You could document the manual instructions and any commands or scripts 
provided in /usr/share/doc/cygwin/emacs.README for reference in every 
release notice, as well as in issues here, rather than documenting it in 
and referring to release notices.

I suggest this as GNU units comes with a python script 
(/usr/bin/units_cur) to update currency exchange rates (requiring 
internet availability to access a few free data sources) if you want to 
use units for such operations, and instructions for various automated 
modes of operation documented in /usr/share/doc/cygwin/units.README, the 
approach decided on after discussions on the apps list.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

Re: Emacs-w32 28.1-2 (marked as test) fails with: "Doing vfork: Resource temporarily unavailable"

[Ken Brown]

On 7/17/2022 12:35 PM, Brian Inglis wrote:
> On 2022-07-17 08:15, Ken Brown wrote:
>> On 7/17/2022 7:08 AM, Oleksandr Gavenko wrote:
>>> 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
> 
>> Please see the release announcement:
>>    https://cygwin.com/pipermail/cygwin-announce/2022-April/010529.html
> 
> Could you not perhaps at emacs (initial) startup add the rebase userpath 
> eln-cache entry,

This is not practical currently because on most Cygwin installations, 
administrator privileges are required to write to /var/lib/rebase/userpath.d, 
but the user(s) running emacs might not have those privileges.  (That's true of 
my own installations, for example.)  But maybe there's a way around that.  Achim?

> and create a shell script to rebase the eln-cache entries which 
> could be e.g. ~/.emacs.d/cygwin-rebase-eln-cache or elsewhere, and perhaps that 
> script could also initially add the rebase userpath eln-cache entry, to make 
> life easier for users.

A script is a good idea.

> You could document the manual instructions and any commands or scripts provided 
> in /usr/share/doc/cygwin/emacs.README for reference in every release notice, as 
> well as in issues here, rather than documenting it in and referring to release 
> notices.

I had actually intended to document it in /usr/share/doc/emacs/README.Cygwin, 
but I apparently forgot to do that.  In the meantime, I've documented it 
upstream, and future emacs releases will contain that documentation in 
/usr/share/emacs/<version>/etc/PROBLEMS.  So I can put a pointer to that 
documentation in release announcements and in /usr/share/doc/emacs/README.Cygwin.

BTW, this may all turn out to be moot, since I don't actually know at the moment 
whether any Cygwin users care about native compilation.  The last paragraph of 
my release announcement asked for feedback from people who try the test release, 
and so far the only feedback has come from someone who didn't read the 
announcement and so didn't know how to use the test release.

Thanks for your suggestions.

Ken