public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Windows 10 updates causes fork retry no child processes
Date: Thu, 03 Nov 2016 19:11:00 -0000	[thread overview]
Message-ID: <878tt0bcpy.fsf@Rainer.invalid> (raw)
In-Reply-To: <581B89B9.6050305@verizon.net> (Gerry Reno's message of "Thu, 03	Nov 2016 15:02:17 -0400")

Gerry Reno writes:
> The installation and applications are 32-bit that we've used for
> years.  The installation is very trimmed down, it is not an
> "everything" install.

Maybe if you'd take the hint about following proper problem reporting that
others have made repeatedly…

> How do I switch them to a 3GB user VM?

With bcdedit, the variable to change is "/uservm=3072" (standard is
2048).  There's a TN article about it.

> The W10 users can clear the problem if they wait some number of
> minutes and keep rebooting their machines.  Eventually after a while
> most of them get the problem to clear but this is a RPITA and it
> frustrates them no end.  One W10 user seems unable to clear their
> problem and we keep uninstalling and reinstalling everything for them.

The problem is quite unlikely to be Cygwin then (and also not the
Windows update), but some other program that maps into the same address
space (most likely one that is using ASLR, which would explain why the
problem can be mitigated by multiple reboots).


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-11-03 19:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 15:47 Gerry Reno
2016-11-02 17:31 ` Evgeny Grin
2016-11-03  0:05   ` Gerry Reno
2016-11-03  5:06 ` Brian Inglis
2016-11-03  6:06   ` Gerry Reno
2016-11-03  7:02     ` Marco Atzeri
2016-11-03 13:01     ` Brian Inglis
2016-11-03 13:42       ` Gerry Reno
2016-11-03 13:46         ` Eliot Moss
2016-11-03 17:08           ` Brian Inglis
2016-11-03 14:31     ` Hans-Bernhard Bröker
2016-11-03 14:58       ` Gerry Reno
2016-11-03 17:28         ` Brian Inglis
2016-11-03 18:33           ` Gerry Reno
2016-11-03 18:47             ` Achim Gratz
2016-11-03 19:02               ` Gerry Reno
2016-11-03 19:11                 ` Achim Gratz [this message]
2016-11-03 22:08             ` Brian Inglis
2016-11-03 22:28               ` Gerry Reno
2016-11-04 18:40               ` Achim Gratz
2016-11-05  0:25                 ` Gerry Reno
2016-11-07 16:17       ` L. A. Walsh
2016-11-03  9:13 ` Marko Božiković

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=878tt0bcpy.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).