X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=ft964OI96Zg0/udFN7wIHt74IJ3L5yluf0kTT+vb2Vn
	XKwYLzedci2dS4cuBkyW4Yu5st/+UHwGO4gAxixxykykeStoBsXJs7hHeoi7Q3Xc
	zMlAsgz/tfKZt/OvB5ymM1II3xEiIxhneCo0eFciooq23XP5aROqfJ+8/qT/thzk
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=oexJztACzDF9M3rm3z56/JNw/20=; b=oSu7C9EWaEaknqD44
	72kWNqN0MmXu7YbFwJWFrfCWDuTnKPmD5OTOeTz7J9JpGGyowto/jazEI2+QpRWt
	trS99iYl2nOHhJ81aWcH5wmxv+EU69kJRFvqSBnUGi0q9OtYoZIKPhTZW9theIe+
	Gd1BySaeqU9S72QdwQ2m0iHPTs=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-2.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Gratz, gratz, business, services
X-HELO:	omr-a020e.mx.aol.com
Message-ID:	<581B89B9.6050305@verizon.net>
Date:	Thu, 03 Nov 2016 15:02:17 -0400
From:	Gerry Reno <greno AT verizon DOT net>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Windows 10 updates causes fork retry no child processes
References:	<581A0AA5 DOT 5030107 AT verizon DOT net> <0d98a082-e270-659f-5b48-b9dfd01fc85f AT SystematicSw DOT ab DOT ca> <581AD3D3 DOT 2020908 AT verizon DOT net> <c7eebf5f-9f33-f5ae-70e7-da586f687725 AT t-online DOT de> <581B508D DOT 4050901 AT verizon DOT net> <3c30f952-23da-bdae-0743-d09320ac87da AT SystematicSw DOT ab DOT ca> <581B82D6 DOT 3020001 AT verizon DOT net> <87d1icbdtx DOT fsf AT Rainer DOT invalid>
In-Reply-To:	<87d1icbdtx.fsf@Rainer.invalid>
x-aol-global-disposition:	G
x-aol-sid:	3039ac1afe6e581b89b9781d
X-AOL-IP:	47.196.166.20
X-IsSubscribed:	yes

On 11/03/2016 02:47 PM, Achim Gratz wrote:
> Gerry Reno writes:
>> I think the simplest way for right now might be to have a batch file
>> run at startup that runs rebaseall.
>>
>> Something like these lines in a batch file:
>> cd C:\Cygwin\bin
>> .\ash /bin/rebaseall
>>
>> This would rebase the dlls each time after Windows Update forces a reboot.
>>
>> Do you see any issue with that?
> You are barking up the wrong tree.  If the Cygwin installation is
> unchanged (as you said it is), then each rebaseall will result in
> exactly the same base addresses for the DLL as before.  So yes, you
> could do what you say (provided that you didn't start any services that
> start Cygwin processes), but it wouldn't help anything.
>
> If your Cygwin installation is too big to fit into the address space
> (likely if it's a 32bit installation and you installed everything), then
> you need to trim it down.  If it's a 32bit Windows, you'll also need to
> switch to a 3GB user VM so the heap gets moved above 2GB.  If it's
> BLODA, you need to stop using it or configure it to stay out of Cygwin's
> business.  The thing that _does_ change each reboot is that any DLL
> using ASLR will end up in a different place until the next reboot, so
> unless you check which DLL you collide with (if it is indeed a collision
> and not an intercept), you'll always get a different Cygwin DLL name
> presented.
>
>
> Regards,
> Achim.

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.

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

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.








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

- Raw text -