X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-498704.7 required=5.0 tests=AWL,BAYES_00
X-Spam-Check-By:	sourceware.org
X-MDAV-Processed:	mail1.multiplay.co.uk, Fri, 17 Jul 2009 23:03:39 +0100
X-Spam-Processed:	mail1.multiplay.co.uk, Fri, 17 Jul 2009 23:03:38 +0100 (not processed: message from trusted or authenticated source)
X-MDRemoteIP:	188.220.16.97
X-Return-Path:	prvs=1449103a4d=killing AT multiplay DOT co DOT uk
X-Envelope-From:	killing AT multiplay DOT co DOT uk
X-MDaemon-Deliver-To:	cygwin AT cygwin DOT com
Message-ID:	<85B57CF2417D454A8F26199F2C90095C@multiplay.co.uk>
From:	"Steven Hartland" <killing AT multiplay DOT co DOT uk>
To:	<cygwin AT cygwin DOT com>
References:	<A5ADE5555FCE437E96E850BA717DFD3D AT multiplay DOT co DOT uk> <20090717182533 DOT GD11740 AT ednor DOT casa DOT cgf DOT cx>
Subject:	Re: maximum number of cygwin processes per user?
Date:	Fri, 17 Jul 2009 23:03:34 +0100
MIME-Version:	1.0
X-IsSubscribed:	yes
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

----- Original Message ----- 
From: "Christopher Faylor"
> 
> The process limit is 256 per program.  You should see an EAGAIN errno
> being set if the process limit is hit.  The overall per-user process
> limit is controlled by Windows.

Hmmm don't quite follow you there Chris, could you elaborate on what you
mean by "per program"?

I'm still trying to determine an error message, I see the new process
being created but it never gets to the first print. This is a perl thing
again so I'm wondering if there are more issues in addition to the SEH
one being discussed in the other thread.

One thing I have seen even with this compile of perl with threads disabled
is a process fork where the created process almost instantly take 2GB.
The forking process then seem to timeout the creation and fork again
and again... Using all memory and cpu in the process over an extended
period of time.

Unfortunately I've not managed to identify a real test case for this
as it seems to happen most frequently when installing new perl modules
via CPAN.

Also noticed that on 2008 64bit, rebase issues are VERY common, something
I've not experienced on XP. I wonder if this has something to do with
what's described as "Address Space Load Randomization" in process explorer?

    Regards
    Steve


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