So, for the sake of a decent argument, here's the idea:

One process spawns another process, which in turn spawns another, that one spawns another, infinitely looping that pattern. The catch is, none of those parent processes stop, they keep looping as well. So that first process keeps spitting out children, those children keep spitting out grandchildren, etc.

This is called a forkbomb. It exploits a feature of modern computer systems called Forking (the process by which one process creates another). Forking is actually really useful for application design, its just when it goes unmonitored that it might end up being an issue.

So, the code.

For the sake of all you batch loving faggots out there, there are these two gems:

and

save either of those as 'mygayforking.bat' and run it. Probably wont crash the system, but you'll get some funny errors.

Now on to some more, real, code.

Thats C source, but it might only be applicable to POSIX though.

Just out of memory in the 2.4 kernel there line that will kill the box some thing like
:;';';';

yeah, the Bash ones were pretty interesting

old news ? Forking can bring a system to its knees any day of the week. Especially if you manage to inject on into a running processes' memory.

haha, gotta love forking. i recently did the "0% | 0%" then saving it as a .bat a few weeks ago. it fucked up my vista, but not XP, strange.

for Unix based OSes (Mac, Linux, but not Windows):
"){ :|:& };:"

Some C coding:
"#include <unistd.h>

int main(int argc, char* args[])
{
while(1)
fork();
return 0;
} "

But "fork()" is not a recognized by Windows and probably will never be. hmmm, funny you brought up forkbombing

why's that funny ? I said POSIX compatible, Windows isnt POSIX compatible. Plus, I don't code for the Windows API.

intresting