DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=bePRhXgZitfx0CSJ
	/wLLbO3nNMoRkC9Hrql14At1hM/qkoVo+JyNfO4xFUZnBs1gWmu700ruSZA+QCR9
	sUav46a2aHFXtFBeBvEBSJ2WfTZUckpUc0IXHdQpUAms5t/rD20Sl/dHdFN6Gn/v
	96dUKNhwyvwlG4OG71xwFSlA0Ek=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: Fork issue on W10 WOW
To: cygwin@cygwin.com
References: <7ad0e0d4-438b-33ad-a711-e0b1996fa6f6@gmail.com> <c1505248-8d03-c0b6-37ca-9c6eed2100e9@cornell.edu> <c618e65c-ab40-287d-39fb-d9daa9ef858a@gmail.com> <20180709090332.GC3111@calimero.vinschen.de> <87e94b8c-13d0-928e-957d-c32b15b8a962@gmail.com> <20180709123739.GB27673@calimero.vinschen.de> <fd7e7ce2-84fd-aef3-b54a-0ff76ef8900c@gmail.com> <CAB8Xom_DX=u0q17ewfRokh_mTcBYMppPZdDLS3UUdaPm5GMV4w@mail.gmail.com> <20180712133847.GT27673@calimero.vinschen.de> <c1aa10ad-e685-f232-6719-5c653f747f83@gmail.com> <874lh17txr.fsf@Rainer.invalid>
From: Marco Atzeri <marco.atzeri@gmail.com>
Message-ID: <c4fc080a-7b31-05d4-990c-668113477f86@gmail.com>
Date: Sat, 14 Jul 2018 17:41:03 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <874lh17txr.fsf@Rainer.invalid>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Am 14.07.2018 um 16:50 schrieb Achim Gratz:
> Marco Atzeri writes:
>> currently I have over 73000000 always busy
>> 73C50000-73C51000 /cygdrive/c/Windows/SysWOW64/cryptbase.dll
>
> What type of Windows do you use?  I have Home N for testing at home and
> Server 2016 plus a bunch of users w/ Enterprise clients (will get one
> myself in a few days) and never seen any such problems.
>
..
>
> Are you using one of the preview update channels or did you use one in
> the past?  Leading up to 1803 MS has apparently tested some new ASLR
> tricks and I don't think they change the settings back to default even
> when you are later switching back to a "normal" release version.
>
> Anyway, with 1803 there is a setting now in the security panel somewhere
> that forces ASLR to be used even when the PE flags say otherwise.  I
> don't know if that can be switched on just for the WoW64 subsystem, but
> it would probably be something you can do via group policy (on a Pro or
> Enterprise client).

Nothing fancy, just vanilla fresh new
W10 64bit Home preinstalled on HP Notebook
German Language
Version 1709
Build system 16299.547

> Regards,
> Achim.

Regards
Marco


---
Diese E-Mail wurde von AVG auf Viren geprüft.
http://www.avg.com


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