Related:

• firehose syndrome n. In mainstream folklore it is observed that trying to drink from a firehose can be a good way to rip your lips off.
  On computer networks, the absence or failure of flow control mechanisms can lead to situations in which the sending system sprays a massive flood of packets at an unfortunate receiving system, more than it can handle....
• buffer overflow: n. What happens when you try to stuff more data into a buffer (holding area) than it can handle.
  This may be due to a mismatch in the processing rates of the producing and consuming processes (see {overrun} and {firehose syndrome}), or because the buffer is simply too small to hold all the data that must accumulate before a piece of it can be processed....
• overrun: n. 1. [techspeak] Term for a frequent consequence of data arriving faster than it can be consumed, esp.
  in serial line communications. For example, at 9600 baud there is almost exactly one character per millisecond, so if a {silo} can hold only two characters and the machine takes longer than 2 msec to get to service the interrupt, at least one character will be lost....
• buffer overflow n. What happens when you try to stuff more data into a buffer (holding area) than it can handle.
  This problem is commonly exploited by crackers to get arbitrary commands executed by a program running with root permissions....
• overrun n. 1. [techspeak] Term for a frequent consequence of data arriving faster than it can be consumed, esp.
  in serial line communications. For example, at 9600 baud there is almost exactly one character per millisecond, so if a silo can hold only two characters and the machine takes longer than 2 msec to get to service the interrupt, at least one character will be lost....
• pam: [from the {MUD} community] vt. 1. To crash a program by overrunning a fixed-size buffer with excessively large input data.
  See also {buffer overflow}, {overrun screw}, {smash the stack}....
• lost in the underflow: adj. Too small to be worth considering
  more specifically, small beyond the limits of accuracy or measurement....
• deadlock: n. 1. [techspeak] A situation wherein two or more processes are unable to proceed because each is waiting for one of the others to do something.
  A common example is a program communicating to a server, which may find itself waiting for output from the server before sending anything more to it, while the server is similarly waiting for more input from the controlling program before outputting anything....
• mailbomb: (also mail bomb) [USENET] 1. v. To send, or urge others to send, massive amounts of {email} to a single system or person, esp.
  with intent to crash or {spam} the recipient's system....