Revision as of 19:43, 4 June 2020 edit Hugovk (talk \| contribs) 93 edits m Link to current version of Python docs ← Previous edit		Revision as of 23:26, 25 July 2020 edit undo Libnoon (talk \| contribs) 59 edits Not releasing a resource is not necessarily a deliberate act; in fact, in most cases it is only a mistake by omission. Next edit →
Line 7: ==Controlling access== The ~~act~~omission of ~~refusing to release~~releasing a resource when a ~~process~~program has finished using it is known as a [[resource leak]], and is an issue in sequential computing. Multiple processes wish to access a limited resource can be an issue in [[concurrent computing]], and is known as [[resource contention]]. Resource management seeks to control access in order to prevent both of these situations.

Resource management (computing): Difference between revisions