X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Wed, 6 Jun 2012 20:29:29 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Windows 8 Release Preview. fork problems with rsync
Message-ID:	<20120606182929.GD30795@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAOLRrpGi-OaejySZ82AVDVzt01mPd0A6gWgjaN60W-sqHZG8cw AT mail DOT gmail DOT com> <20120606123434 DOT GA27662 AT calimero DOT vinschen DOT de> <CAOLRrpHQV2JcaK_f1UAEFR33ga=w8hqdNUSEqfZj1ygKXMCVoA AT mail DOT gmail DOT com> <20120606161217 DOT GB30795 AT calimero DOT vinschen DOT de> <CADSoG1tvx3dPMAZ8-CppoEemqU8ObDuj+4JySTGgSvK-LSYkUg AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CADSoG1tvx3dPMAZ8-CppoEemqU8ObDuj+4JySTGgSvK-LSYkUg@mail.gmail.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

Please, don't http://cygwin.com/acronyms/#TOFU 
Thank you.

On Jun  6 17:59, Nick Lowe wrote:
> > Thanks.  I can confirm the effect.  For no apparent reason, the OS
> > reserves a 1 Megs shared memory region, top-down allocated, of which it
> > uses about 20K.  It's not the PEB or one of the TEBs, though.  Nor is
> > it a thread stack.  I checked, and it turns out that it's allocated
> > in every process, on 32 and 64 bit systems.  That's kind of worrying
> > since that's bound to collide with mmaped regions and pthread stacks a
> > lot.  I don't know what to do at this point.
> 
> Urgh! Hmm.. Do you see the same effect when running the process in
> question under the Windows 8 operating system context?
> 
> If you manifest and include:
> 
> <compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
>       <application>
>          <!--The ID below indicates application support for Windows Vista -->
> <supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}"/>
> <!--The ID below indicates application support for Windows 7 -->
> <supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}"/>
> <!--The ID below indicates application support for Windows 8 -->
> <supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}"/>
>       </application>
>   </compatibility>
> http://msdn.microsoft.com/en-us/library/windows/desktop/hh848036(v=vs.85).aspx
> 
> Does the odd behaviour still persist?

Yes.

> Could it be possibly be something to do with the fault tolerant heap
> (FTH) and changes they've made to it? I would try ensuring that is
> switched off too...

That's not the problem either.  This problem also occurs on the 2012
server which doesn't run FTH.

But thanks for any idea.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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