+++ This bug was initially created as a clone of Bug #456235 +++ I'm assuming this is a similar case to bug 456235, and I'm not going to verify/narrow this leak myself. (My first "to-be-verified" guess would be http://hg.mozilla.org/dom-inspector/rev/894241f24e4e though I wouldn't know why it would trigger a new leak.) ***** http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1222443389.1222447850.3623.gz Linux comm-central dep unit test on 2008/09/26 08:36:29 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1222447550.1222451963.12992.gz Linux comm-central dep unit test on 2008/09/26 09:45:50 (mochitest not triggered: expected for now, see bug 450983 comment 30.) TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 8636 bytes during test execution (should have leaked no more than 8568 bytes) TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 8756 bytes during test execution (should have leaked no more than 8688 bytes) *** http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1222442712.1222447955.3840.gz MacOSX 10.4 comm-central dep unit test on 2008/09/26 08:25:12 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1222447656.1222452914.15127.gz MacOSX 10.4 comm-central dep unit test on 2008/09/26 09:47:36 TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 21496 bytes during test execution (should have leaked no more than 21428 bytes) TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 8648 bytes during test execution (should have leaked no more than 8580 bytes) TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 8768 bytes during test execution (should have leaked no more than 8700 bytes) *** http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1222446736.1222450706.9989.gz Win2k3 comm-central dep unit test on 2008/09/26 09:32:16 http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1222450407.1222454334.18286.gz Win2k3 comm-central dep unit test on 2008/09/26 10:33:27 TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 21561 bytes during test execution (should have leaked no more than 21493 bytes) TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 8593 bytes during test execution (should have leaked no more than 8525 bytes) TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 8713 bytes during test execution (should have leaked no more than 8645 bytes)

$ hg push pushing to ssh://hg.mozilla.org/build/buildbot-configs searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 1 changesets with 1 changes to 1 files $ hg tip -v changeset: 375:27419b9a859e tag: tip user: Justin Wood <Callek@gmail.com> date: Sat Sep 27 22:26:50 2008 -0400 files: seamonkey-unittest/config.py description: Update leak thresholds to turn stuff green again, we really need to trend these down sooner than later... I'll push these to the machines shortly.

3 greens with exact new values. V.Fixed

Don't ask me what is going on, but this leak went away with http://hg.mozilla.org/dom-inspector/rev/504264d49df6 which is the only checkin between (for example) http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1223069959.1223074058.7840.gz&fulltext=1 Win2k3 comm-central dep unit test on 2008/10/03 14:39:19 and http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1223077010.1223081081.28742.gz&fulltext=1 Win2k3 comm-central dep unit test on 2008/10/03 16:36:50 Now, need to decrease/restore threshold by 68 bytes :->