Call superclass's TearDown to avoid leaks.

chrome/browser/cocoa/blocked_popup_container_controller_unittest.mm

Index: chrome/browser/cocoa/blocked_popup_container_controller_unittest.mm
===================================================================
--- chrome/browser/cocoa/blocked_popup_container_controller_unittest.mm	(revision 19765)
+++ chrome/browser/cocoa/blocked_popup_container_controller_unittest.mm	(working copy)
@@ -20,8 +20,6 @@
 
 class BlockedPopupContainerControllerTest : public RenderViewHostTestHarness {
  public:
-  CocoaTestHelper cocoa_helper_;  // Inits Cocoa, creates window, etc...
-
   virtual void SetUp() {
     RenderViewHostTestHarness::SetUp();
     container_ = BlockedPopupContainer::Create(contents(), profile());
@@ -34,9 +32,10 @@
 
   virtual void TearDown() {
     // This will also signal the Cocoa controller to delete itself with a
-    // Destroy() mesage to the bridge.
+    // Destroy() mesage to the bridge. It also clears out the association with
+    // |contents_|.
     container_->Destroy();
-    contents_->set_blocked_popup_container(NULL);
+    RenderViewHostTestHarness::TearDown();
   }
 
   TabContents* BuildTabContents() {