fix(snack-bar): prevent error when opening multiple snack bars in fas…

…t succession

Fixes a runtime error being thrown by Angular when opening multiple snack bars, that have a timeout, in quick succession. The fix waits for the zone to settle before firing the final callbacks.

**Note on testing:** This change is missing a unit test, because I couldn't find a way to trigger the error during tests, however the approach is similar to angular#2219.

Fixes angular#2390.

src/lib/snack-bar/snack-bar-container.ts

@@ -92,11 +92,9 @@ export class MdSnackBarContainer extends BasePortalHost implements OnDestroy {
   /** Handle end of animations, updating the state of the snackbar. */
   onAnimationEnd(event: AnimationTransitionEvent) {
     if (event.toState === 'void' || event.toState === 'complete') {
-      this._ngZone.run(() => {
-        this.onExit.next();
-        this.onExit.complete();
-      });
+      this._completeExit();
     }
+
     if (event.toState === 'visible') {
       this._ngZone.run(() => {
         this.onEnter.next();
@@ -131,8 +129,14 @@ export class MdSnackBarContainer extends BasePortalHost implements OnDestroy {
    * Makes sure the exit callbacks have been invoked when the element is destroyed.
    */
   ngOnDestroy() {
-    // Wait for the zone to settle before removing the element. Helps prevent
-    // errors where we end up removing an element which is in the middle of an animation.
+    this._completeExit();
+  }
+
+  /**
+   * Waits for the zone to settle before removing the element. Helps prevent
+   * errors where we end up removing an element which is in the middle of an animation.
+   */
+  private _completeExit() {
     this._ngZone.onMicrotaskEmpty.first().subscribe(() => {
       this.onExit.next();
       this.onExit.complete();