Opened 6 years ago

Closed 6 years ago

#9851 closed bug (fixed)

Forkbomb creates Kernel Screen of Death

Reported by: mdickie Owned by: axeld
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/alpha4.1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All


/* Compile using gcc forkbomb.c -o forkbomb */
#include <unistd.h>
int main()
  return 0;

Tested on VirtualBox which needs multiple instances of the forkbomb. Using

:(){  forkbomb|forkbomb& };:

After some times typing it Kernel Screen of Death appears.

Also tested on an old Notebook PC Dell Latitude C640 but there you simply have to run forkbomb. BTW: It would be great if haiku would call the Screen of Death KSOD.

Attachments (1)

haiku-kdl.png (25.3 KB) - added by mdickie 6 years ago.
Forkbomb Haiku KDL

Download all attachments as: .zip

Change History (4)

comment:1 Changed 6 years ago by anevilyak

Component: - GeneralSystem/Kernel
Owner: changed from nobody to axeld

What's the actual panic message/backtrace? As an aside, the name KDL is specifically a BeOS reference.

Changed 6 years ago by mdickie

Attachment: haiku-kdl.png added

Forkbomb Haiku KDL

comment:2 Changed 6 years ago by mdickie

I attached an image because I don't know where I can read out the message/backtrace for Haiku.

Last edited 6 years ago by mdickie (previous) (diff)

comment:3 Changed 6 years ago by bonefish

Resolution: fixed
Status: newclosed

Fixed in hrev45811.

Note: See TracTickets for help on using tickets.