in reply to win32+fork "Application Error", bug?

I don't think a fork while 1 style application should er... not cause a memory error. You've instructed your computer to fork as fast as it can, apparently before it can get to the die 2. It consumes all your memory and that'd be why you have to hit the three finger salute.

-Paul

Replies are listed 'Best First'.
Re^2: win32+fork "Application Error", bug?
by bart (Canon) on Jan 10, 2007 at 12:17 UTC
    Indeed.

    This kind of junk is commonly called a "fork bomb". I don't think it's even reasonable to expect that this will behave nicely. 

    fork or die while 1;

    [download]
    might behave just a little bit better.
[reply]
[d/l]

In Section Seekers of Perl Wisdom