Skip to main content
Code Golf

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • \$\begingroup\$ Darn it :D I just had the same idea :P \$\endgroup\$ Commented May 28, 2014 at 8:22
  • 2
    \$\begingroup\$ :(){ :&};: shouldn't eat your memory. It stops as soon as it has forked, so there's only ever O(1) active. You've done while(fork());, what would eat your memory linearly is the equivalent of fork(); while(1);. \$\endgroup\$ Commented May 28, 2014 at 9:28
  • 32
    \$\begingroup\$ Wow! those are some deadly emoticions! I best not call my computer bignosed frownyface :(){ .... \$\endgroup\$ Commented May 28, 2014 at 22:27
  • 1
    \$\begingroup\$ If I remember correctly... the fork bomb periodically leaves one PID open. The script can be run again in that interval... and if that doesn't count, it is possible to kill all the forks with some effort. Rebooting is simply the easiest solution. \$\endgroup\$ Commented May 30, 2014 at 21:53
  • 14
    \$\begingroup\$ I don't think this qualifies. It doesn't make it impossible for the script to run again, instead it guarantees that it runs again (many times). \$\endgroup\$ Commented May 31, 2014 at 19:45