Deadlock (computer science) in the context of Distributed computing

An arbitral tribunal or arbitration tribunal, also arbitration commission, arbitration committee or arbitration council is a panel of adjudicators which is convened and sits to resolve a dispute by way of arbitration. The tribunal may consist of a sole arbitrator, or there may be two or more arbitrators, which might include a chairperson or an umpire. The tribunal usually consists of an odd number of arbitrators. Members selected to serve on an arbitration panel are typically professionals with expertise in both law and in friendly dispute resolution (mediation). Some scholars have suggested that the ideal composition of an arbitration commission should include at least also one professional in the field of the disputed situation, in cases that involve questions of asset or damages valuation for instance an economist.

The parties to agree on arbitration are usually free to determine the number and composition of the arbitral tribunal. Many jurisdictions have laws with general rulings in arbitration, they differ as to how many arbitrators should constitute the tribunal if there is no agreement. In some legal systems, an arbitration clause which provides for an even number of arbitrators is understood to imply that the appointed arbitrators will select an additional arbitrator as a chairperson, to avoid deadlock arising.

Automatic Reference Counting (ARC) is a memory management feature of the Clang compiler providing automatic reference counting for the Objective-C and Swift programming languages. At compile time, it inserts into the object code messages retain and release which increase and decrease the reference count at run time, marking for deallocation those objects when the number of references to them reaches zero.

ARC differs from tracing garbage collection in that there is no background process that deallocates the objects asynchronously at runtime. Unlike tracing garbage collection, ARC does not handle reference cycles automatically. This means that as long as there are "strong" references to an object, it will not be deallocated. Strong cross-references can accordingly create deadlocks and memory leaks. It is up to the developer to break cycles by using weak references.