An attacker utilizes a resource leak on the target to deplete the quantity
						of the resource available to service legitimate requests. Resource leaks
						most often come in the form of memory leaks where memory is allocated but
						never released after it has served its purpose, however, theoretically, any
						other resource that can be reserved can be targeted if the target fails to
						release the reservation when the reserved resource block is no longer
						needed. In this attack, the attacker determines what activity results in
						leaked resources and then triggers that activity on the target. Since some
						leaks may be small, this may require a large number of requests by the
						attacker. However, this attack differs from a flooding attack in that the
						rate of requests is generally not significant. This is because the lost
						resources due to the leak accumulate until the target is reset, usually by
						restarting it. Thus, a resource-poor attacker who would be unable to flood
						the target can still utilize this attack.