Bommels05/Mozilla
Bommels05/Mozilla
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Don't unlink so aggressively. Bug 398083, r+sr+a=sicking

Browse Source 
git-svn-id: svn://10.0.0.236/trunk@237073 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
bzbarsky%mit.edu 2007-10-02 14:40:39 +00:00
parent 511ddb65c3
commit 6c25c9877d
1 changed files with 0 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
mozilla/content/xbl/src/nsXBLPrototypeBinding.cpp
View File

@ -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