The nsStr::EnsureCapacity function call theAgent-Realloc without checking the return. Which may cause memory leak. It will crash if it return NULL or value other than aString since the theAgent->Realloc may free the origional aString It will leak the newly allocate memory if the return value is different from aString. I have not see it leak form purify. Only whitebox review code let me enter this bug. 111 void nsStr::EnsureCapacity(nsStr& aString,PRUint32 aNewLength,nsIMemoryAgent* anAgent) { 112 if(aNewLength>aString.mCapacity) { 113 nsIMemoryAgent* theAgent=(anAgent) ? anAgent : GetDefaultAgent(); 114 theAgent->Realloc(aString,aNewLength); 115 AddNullTerminator(aString); 116 } 117 }

This is not a valid bug, but the problem where nsStr needs to be more defensive in case of memory allocation failure is true. Marking as dup. *** This bug has been marked as a duplicate of 12061 ***

*** This bug has been marked as a duplicate of 12861 ***

verified duplicate of 12861