Closed Bug 463355 Opened 16 years ago Closed 16 years ago

SeaMonkey reports "mochitest" leak increase(s) since 2008/11/04

Categories

(SeaMonkey :: Build Config, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
seamonkey2.0a2

People

(Reporter: sgautherie, Assigned: kairo)

References

Details

(Keywords: memory-leak, regression)

See Linux/MacOSX/Windows current "unit test" tinderboxes. NB: There may have been "multiple" leaks in the timeframe, with has lots of other orange/red too :-/ PS: Bug 462937 should be unrelated, but makes this more(/too) painful to narrow down for now.
No longer depends on: 462937
{ [kairo@kairo.at - 2008/11/13 05:53:39] bumped leak thresholds to make the boxes go green for their next cycles } The boxes are now green. Is this a temporary workaround or the actual "fix" ?
(In reply to comment #1) > Is this a temporary workaround or the actual "fix" ? From his comment I'd suspect its a workaround to turn the boxes green so we don't regress more. If these are c-c commits we should get/have bugs filed, if they are m-c that don't affect FF we should get bugs filed and see how we can go about fixing them. If they are m-c commits that *do* affect Firefox, perhaps we should backout or block FF-release on them (I'm no driver)
Blocks: 450983
(In reply to comment #1) http://hg.mozilla.org/build/buildbot-configs/rev/2426c33efdfa (In reply to comment #2) Well, this is the bug to look into the issue (for now). I/Someone still have to look into what the new leaks actually are...
Flags: blocking-seamonkey2?
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1b2pre) Gecko/20081116 SeaMonkey/2.0a2pre] (home, optim default) (W2Ksp4) (http://hg.mozilla.org/mozilla-central/rev/8b3caddca8f5 +http://hg.mozilla.org/comm-central/rev/ebcb28433bfe) It turns out to be bug 391318: on my Windows 2000, (true numbers may be different...) mochi increased by "712", chrome and browser increased by "8".
Assignee: nobody → kairo
No longer blocks: mlkTests, 450983
Status: NEW → RESOLVED
Closed: 16 years ago
Component: General → Build Config
Depends on: 391318, 450983
Flags: blocking-seamonkey2?
QA Contact: general → build-config
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0a2
You need to log in before you can comment on or make changes to this bug.