From 6c25c9877d934bbbf82a4cd91c81ccb17c2c6d99 Mon Sep 17 00:00:00 2001
From: "bzbarsky%mit.edu"
 <bzbarsky%mit.edu@18797224-902f-48f8-a5cc-f745e15eee43>
Date: Tue, 2 Oct 2007 14:40:39 +0000
Subject: [PATCH] Don't unlink so aggressively.  Bug 398083, r+sr+a=sicking

git-svn-id: svn://10.0.0.236/trunk@237073 18797224-902f-48f8-a5cc-f745e15eee43
---
 mozilla/content/xbl/src/nsXBLPrototypeBinding.cpp | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/mozilla/content/xbl/src/nsXBLPrototypeBinding.cpp b/mozilla/content/xbl/src/nsXBLPrototypeBinding.cpp
index f41c948e0f1..df0344674ab 100644
--- a/mozilla/content/xbl/src/nsXBLPrototypeBinding.cpp
+++ b/mozilla/content/xbl/src/nsXBLPrototypeBinding.cpp
@@ -368,20 +368,8 @@ nsXBLPrototypeBinding::Traverse(nsCycleCollectionTraversalCallback &cb) const
 void
 nsXBLPrototypeBinding::Unlink()
 {
-  mBinding = nsnull;
   if (mImplementation)
     mImplementation->Unlink();
-  if (mResources)
-    NS_IF_RELEASE(mResources->mLoader);
-
-  // I'm not sure whether it would be safer to just nuke the tables or to
-  // traverse them with unlinking functions...  or whether we even need to
-  // unlink them.  I think we need to at least clean up mInsertionPointTable
-  // becase it can hold strong refs to nodes in the binding document.
-  delete mInsertionPointTable;
-  mInsertionPointTable = nsnull;
-  delete mInterfaceTable;
-  mInterfaceTable = nsnull;
 }
 
 void