nsCRT::free(char * 0xcdcdcdcd) line 179 + 9 bytes nsCookie::~nsCookie() line 75 + 13 bytes nsCookie::`scalar deleting destructor'() + 15 bytes nsCookie::Release(nsCookie * const 0x03edf040) line 46 + 183 bytes XPCWrappedNative::~XPCWrappedNative() line 547 + 18 bytes XPCWrappedNative::`scalar deleting destructor'(unsigned int 1) + 15 bytes XPCWrappedNative::Release(XPCWrappedNative * const 0x03edefc0) line 777 + 147 bytes XPCWrappedNative::FlatJSObjectFinalized(JSContext * 0x004f4e70, JSObject * 0x014a42e0) line 897 XPC_WN_NoHelper_Finalize(JSContext * 0x004f4e70, JSObject * 0x014a42e0) line 630 js_FinalizeObject(JSContext * 0x004f4e70, JSObject * 0x014a42e0) line 1840 + 96 bytes js_GC(JSContext * 0x004f4e70, unsigned int 5) line 1311 + 11 bytes Note that some code does check for null values (especially getters). + cookieName 0xcdcdcdcd "" + cookieValue 0xcdcdcdcd "" + cookieHost 0xcdcdcdcd "" + cookiePath 0xcdcdcdcd ""

Comment on attachment 106268 [details] [diff] [review] initialize the values and check for null before freeing them can you use nsnull rather than null to make it clear you're init'ing a pointer?

checked in

verified patch checked in with lxr on mozilla trunk, values are initialized and free'd properly