WORKFLOW-BASED OBJECT DESTRUCTION

Objects in a computing environment are often utilized by threads through an object lifecycle, and are destroyed at the end of the object lifecycle to reclaim the computing resources used by the object. In some cases, a thread that initiates an object destruction of an object may be unable to complete the destruction (e.g., a second thread may hold a synchronization lock over an object resource of the object). An object destruction workflow initiates the destruction of an object on behalf of a thread. If the object destruction workflow encounters a failure to complete the object destruction, a new reference to the object is inserted into an object destruction list, as the last reference to the object. A second thread discovers and releases the last reference in the object destruction list, prompting the object destruction workflow to resume the attempt to destroy the object on behalf of the second thread.