Re: forking issue on Windows XP?

On Sun June 5 2005 18:50, Max T. Woodbury wrote:
> 
> > Use the performance monitor graph to track "free page table entries" -
> 
> Good idea.  I haven't tried that yet.  I was thinking it might be a
> fragmented heap, but that could also be the cause...
> 
Try the scripts in my recent post, more selection of things to
break.  You can allocate little or big chunks of memory.  You
can wait for the whole tree to build before anything terminates.
I expect that will leave a chain of broken sh.exe's in memory.

Sneak up on the range 7-9 slowly, do not redirect to a disk
file unless you have run (and been able to recover from) any
test setup first.

Obvious reason - you don't want to have to pull the plug while
it is writing to the disk.

Avoid the "must increase virtual memory" state - that is known
to crater msys.dll  Go at least 1.5 to 2.0 times physical for swap
space.

-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20