Closed
Bug 126364
Opened 23 years ago
Closed 23 years ago
Mail leaks up after this checkin
Categories
(MailNews Core :: Backend, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 102229
People
(Reporter: mcafee, Assigned: mscott)
Details
(Keywords: memory-leak, regression)
Second jump in mail leaks today:
http://bonsai.mozilla.org/cvsquery.cgi?module=MozillaTinderboxAll&date=explicit&mindate=1014096720&maxdate=1014099959
--NEW-LEAKS-----------------------------------leaks------leaks%-----------------------
GlobalWindowImpl 200 -
nsCodebasePrincipal 60 -
nsXPCComponents_Interfaces 20 -
BackstagePass 16 -
nsJSRuntimeServiceImpl 20 -
nsGenericFactory 16 -
nsJSID 32 -
AtomImpl 24 -
nsSimpleURI 4 -
nsXPCComponents_ID 12 -
nsLocalFile 432 -
nsXPCComponents_Results 12 -
si_SignonUserStruct 8 -
nsJSIID 100 -
XPCWrappedNativeProto 224 -
xptiWorkingSet 52 -
si_SignonURLStruct 16 -
nsSupportsArray 52 -
nsSystemPrincipal 48 -
nsPrefBranch 64 -
nsHashtable 88 -
xptiInterfaceInfo 80 -
nsXBLDocGlobalObject 24 -
si_SignonDataStruct 584 -
nsAggregatePrincipal 68 -
xptiInterfaceInfoManager 152 -
NavigatorImpl 24 -
nsDOMClassInfo 112 -
XPCNativeScriptableInfo 64 -
nsComponentManagerImpl 160 -
nsXPCComponents_Classes 12 -
nsPrefService 36 -
nsTimerImpl 36 -
SharedScriptableHelperForJSIID 8 -
xptiFile 3668 -
morkObject 40 -
nsEntropyCollector 1044 -
XPCWrappedNative 572 1200.00%
XPCNativeScriptableShared 836 1000.00%
nsStr 204 466.67%
nsVoidArray 88 266.67%
nsXPCComponents 132 200.00%
nsThread 48 100.00%
Reporter | ||
Updated•23 years ago
|
Keywords: mlk,
regression
Comment 1•23 years ago
|
||
I'm pretty sure it's not mine. My back end changes were backed out due to
orangeness on btek and comet and the front end error reporting changes will
never be executed because, right now, the back end will never return an error.
Comment 2•23 years ago
|
||
It wasn't me. My checkin was a string change to a feature that's turned off.
(time bomb)
Assignee | ||
Comment 3•23 years ago
|
||
The first jump in mail leaks I think was due to jband's checkin. There already
is a long discussion about that. Apparently it is from an existing leak which is
now holding on to more objects down in xp-connect. That's the jump from 5kb to
9kb. As Chris mentioned when he filed this bug, this bug is tracking the 9kb to
14kb jump.
Just stating the obvious.
Assignee | ||
Comment 4•23 years ago
|
||
From what I can tell, the only code checked in during this window that has a
chance to effect leaks for the mail tests would be:
ducarroz's mime checkins
and
gordon's cache checkins
Are we talking about the same leaks as bug 126455, or are these leak numbers
from a different test?
Assignee | ||
Comment 6•23 years ago
|
||
Jean-Francois backed out his code and it had no effect on the leak numbers.
Thanks for trying JF. Feel free to check your mime changes back in.
That leaves us with the cache changes.
Ahh I just read gordon's comments. Yes indeed they look like the same set of
leaks that are already reported in bug 126455. Note the checkin logs for this
leak and the one on brad are nearly identical. I'm sure this is a dup.
*** This bug has been marked as a duplicate of 126455 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified (it was gordon, apparently).
Status: RESOLVED → VERIFIED
re-opening to re-resolve this.
Status: VERIFIED → REOPENED
Resolution: DUPLICATE → ---
dup of 102229, by way of dup bug 126455
*** This bug has been marked as a duplicate of 102229 ***
Status: REOPENED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•