goog.Disposable

Invokes a callback function when this object is disposed. Callbacks are invoked in the order in which they were added. If a callback is added to an already disposed Disposable, it will be called immediately.

Disposes of the object. If the object hasn't already been disposed of, calls #disposeInternal. Classes that extend goog.Disposable should override #disposeInternal in order to cleanup references, resources and other disposable objects. Reentrant.

Performs appropriate cleanup. See description of goog.disposable.IDisposable for examples. Classes that extend goog.Disposable should override this method. Not reentrant. To avoid calling it twice, it must only be called from the subclass' disposeInternal method. Everywhere else the public dispose method must be used. For example:

 mypackage.MyClass = function() {
 mypackage.MyClass.base(this, 'constructor');
     // Constructor logic specific to MyClass.
     ...
   };
   goog.inherits(mypackage.MyClass, goog.Disposable);

   mypackage.MyClass.prototype.disposeInternal = function() {
     // Dispose logic specific to MyClass.
     ...
     // Call superclass's disposeInternal at the end of the subclass's, like
     // in C++, to avoid hard-to-catch issues.
     mypackage.MyClass.base(this, 'disposeInternal');
   };
 

Associates a disposable object with this object so that they will be disposed together.

If monitoring the goog.Disposable instances is enabled, stores the creation stack trace of the Disposable instance.

Clears the registry of undisposed objects but doesn't dispose of them.

Returns True if we can verify the object is disposed. Calls isDisposed on the argument if it supports it. If obj is not an object with an isDisposed() method, return false.

Whether to attach creation stack to each created disposable instance; This is only relevant for when MonitoringMode != OFF.

The monitoring mode of the goog.Disposable instances. Default is OFF. Switching on the monitoring is only recommended for debugging because it has a significant impact on performance and memory usage. If switched off, the monitoring code compiles down to 0 bytes.