On 8/28/2020 1:39 PM, Corinna Vinschen wrote:
On Aug 28 12:02, Ken Brown via Cygwin wrote:
On 8/28/2020 9:36 AM, Corinna Vinschen wrote:
As POC, I added a bit of code to maintain a second array, which is only
allocated (using HeapAlloc so as not to spill into the child processes)
Should there
On Aug 28 12:02, Ken Brown via Cygwin wrote:
> On 8/28/2020 9:36 AM, Corinna Vinschen wrote:
> > As POC, I added a bit of code to maintain a second array, which is only
> > allocated (using HeapAlloc so as not to spill into the child processes)
>
> Should there be a call to HeapFree somewhere, or
On 8/28/2020 9:36 AM, Corinna Vinschen wrote:
As POC, I added a bit of code to maintain a second array, which is only
allocated (using HeapAlloc so as not to spill into the child processes)
Should there be a call to HeapFree somewhere, or is there some reason this isn't
needed?
Ken
--
Proble
Hi all
> > > > > > > It seems like there's a limit of the number of possible
> > > > > > > child processes defined to 256 with 'NPROCS' in
> > > > > > > //winsup/cygwin/child_info.h used in 'cprocs' in
> > > > > > > //winsup/cygwin/sigproc.cc
> > > > > > >
> > > > > > > 256 is quite few possible c
On Aug 28 08:29, Ken Brown via Cygwin wrote:
> On 8/28/2020 4:38 AM, sten.kristian.ivars...@gmail.com wrote:
> > > > > > It seems like there's a limit of the number of possible child
> > > > > > processes defined to 256 with 'NPROCS' in
> > > > > > //winsup/cygwin/child_info.h used in 'cprocs' in
>
On 8/28/2020 4:38 AM, sten.kristian.ivars...@gmail.com wrote:
Hi Corinna
Dear cygwin folks
It seems like there's a limit of the number of possible child
processes defined to 256 with 'NPROCS' in
//winsup/cygwin/child_info.h used in 'cprocs' in
//winsup/cygwin/sigproc.cc
256 is quite few possi
> > Hi Corinna
> >
> >>> Dear cygwin folks
> >>>
> >>> It seems like there's a limit of the number of possible child
> >>> processes defined to 256 with 'NPROCS' in
> >>> //winsup/cygwin/child_info.h used in 'cprocs' in
> >>> //winsup/cygwin/sigproc.cc
> >>>
> >>> 256 is quite few possible children
On Aug 27 21:42, Ken Brown via Cygwin wrote:
> On 8/27/2020 8:17 AM, Kristian Ivarsson via Cygwin wrote:
> > Hi Corinna
> >
> > > > Dear cygwin folks
> > > >
> > > > It seems like there's a limit of the number of possible child
> > > > processes defined to 256 with 'NPROCS' in //winsup/cygwin/chi
On 8/27/2020 8:17 AM, Kristian Ivarsson via Cygwin wrote:
Hi Corinna
Dear cygwin folks
It seems like there's a limit of the number of possible child
processes defined to 256 with 'NPROCS' in //winsup/cygwin/child_info.h
used in 'cprocs' in //winsup/cygwin/sigproc.cc
256 is quite few possible
Hi Corinna
> > Dear cygwin folks
> >
> > It seems like there's a limit of the number of possible child
> > processes defined to 256 with 'NPROCS' in //winsup/cygwin/child_info.h
> > used in 'cprocs' in //winsup/cygwin/sigproc.cc
> >
> > 256 is quite few possible children in an enterprise environme
On Aug 26 14:00, Kristian Ivarsson via Cygwin wrote:
> Dear cygwin folks
>
> It seems like there's a limit of the number of possible child processes
> defined to 256 with 'NPROCS' in //winsup/cygwin/child_info.h used in
> 'cprocs' in //winsup/cygwin/sigproc.cc
>
> 256 is quite few possible childr
Dear cygwin folks
It seems like there's a limit of the number of possible child processes
defined to 256 with 'NPROCS' in //winsup/cygwin/child_info.h used in
'cprocs' in //winsup/cygwin/sigproc.cc
256 is quite few possible children in an enterprise environment and perhaps
the limit should be lim
12 matches
Mail list logo