Closed
Bug 493547
Opened 16 years ago
Closed 15 years ago
[SeaMonkey, cn-sea-qm-win2k3-01] crashtest: new 188 bytes leak, including nsPluginHostImpl, on 2009/05/17 after big new tests landing
Categories
(SeaMonkey :: Build Config, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.0b2
People
(Reporter: sgautherie, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: memory-leak)
Attachments
(1 obsolete file)
First build is:
{
http://tinderbox.mozilla.org/showlog.cgi?log=SeaMonkey/1242616339.1242620567.15305.gz
WINNT 5.2 comm-central unit test on 2009/05/17 20:12:19
TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 188 bytes during test execution
TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 1 instance of nsLocalFile with size 88 bytes
TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 1 instance of nsPluginHostImpl with size 88 bytes
TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 1 instance of nsStringBuffer with size 8 bytes
TEST-UNEXPECTED-FAIL | runtests-leaks | leaked 1 instance of nsVoidArray with size 4 bytes
}
Regression timeframe:
http://hg.mozilla.org/releases/mozilla-1.9.1/pushloghtml?startdate=2009-05-17+16%3A17%3A21&enddate=2009-05-17+20%3A09%3A20
To be noted: Windows SeaMonkey-Ports is still green.!.
Flags: wanted1.9.1?
Reporter | ||
Updated•16 years ago
|
Summary: [SeaMonkey, Windows] New 188 bytes leak on 2009/05/17, after big new tests landing → [SeaMonkey, Windows] New 188 bytes leak on 2009/05/17, including nsPluginHostImpl, after big new tests landing
Reporter | ||
Updated•16 years ago
|
Reporter | ||
Comment 1•16 years ago
|
||
[Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.2a1pre) Gecko/20090518 SeaMonkey/2.0b1pre] (experimental/_m-c_, home, optim default) (W2Ksp4)
(http://hg.mozilla.org/mozilla-central/rev/a7c0b3588242
+http://hg.mozilla.org/comm-central/rev/6786ebf24275 + bug 493008 patches)
Fwiw, I don't reproduce it locally.
It looks like to be specific to this machine:
related to some (bad / badly handled) plugin?
Summary: [SeaMonkey, Windows] New 188 bytes leak on 2009/05/17, including nsPluginHostImpl, after big new tests landing → [SeaMonkey, Windows] crashtest: new 188 bytes leak, including nsPluginHostImpl, on 2009/05/17 after big new tests landing
Comment 2•16 years ago
|
||
Yes, this looks somewhat strange, esp. as the boxes in SeaMonkey-Ports, which are testing the same code, are passing crashtests without failures.
Reporter | ||
Comment 3•16 years ago
|
||
KaiRo, I would suggest, ftb, to code (in buildbot factory and config) and use a crashtest leak threshold...
Reporter | ||
Comment 4•16 years ago
|
||
KaiRo, could you compare <about:plugins> on SeaMonkey and SeaMonkey-Ports boxes?
Comment 5•16 years ago
|
||
about:plugins is identical on builds from both buildbot configs.
Reporter | ||
Comment 6•16 years ago
|
||
Though I'd like to figure this out,
I guess you don't have much time to spend on this issue,
so the best course of action will be to just WontFix this after you have moved the new boxes to production...
Reporter | ||
Comment 7•16 years ago
|
||
R.WontFix, now that the box(es) has been recycled.
Status: NEW → RESOLVED
Closed: 16 years ago
Flags: wanted1.9.1?
Resolution: --- → WONTFIX
Reporter | ||
Comment 8•15 years ago
|
||
It looks like cn-sea-qm-win2k3-01 has actually been reused and is still leaking.
What would be the difference from cb-seamonkey-win32-01 and cb-seamonkey-win32-02 which don't leak?
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Summary: [SeaMonkey, Windows] crashtest: new 188 bytes leak, including nsPluginHostImpl, on 2009/05/17 after big new tests landing → [SeaMonkey, cn-sea-qm-win2k3-01] crashtest: new 188 bytes leak, including nsPluginHostImpl, on 2009/05/17 after big new tests landing
Reporter | ||
Updated•15 years ago
|
Status: REOPENED → NEW
Comment 9•15 years ago
|
||
(In reply to comment #8)
> It looks like cn-sea-qm-win2k3-01 has actually been reused and is still
> leaking.
Sure it was "reused", the plan was to join the old VMs to the new pools all along, or else we wouldn't have/get the machine power to run multiple trees. It's interesting that it's still leaking, though.
> What would be the difference from cb-seamonkey-win32-01 and
> cb-seamonkey-win32-02 which don't leak?
I have no clue, I don't actually know of any difference.
Reporter | ||
Comment 10•15 years ago
|
||
Work around the leak until we get a better solution.
Attachment #388913 -
Flags: review?(kairo)
Comment 11•15 years ago
|
||
Not sure if I like it, and I really want to know what's up with that box. In addition, we want to upgrade Java anyway, which will change some things regarding plugins, which this is related to, so I'd rather leave this as it is until I come around to care about this Java upgrade. And for this week, I don't care about anything but Beta 1 anyhow. ;-)
Reporter | ||
Updated•15 years ago
|
Depends on: 503807
Product: Core → SeaMonkey
QA Contact: general → general
Version: 1.9.1 Branch → Trunk
Reporter | ||
Comment 12•15 years ago
|
||
Bug 503807 fixed this. (Unless bug 471647 would now be "masking" it.)
Status: NEW → RESOLVED
Closed: 16 years ago → 15 years ago
Component: General → Build Config
Flags: in-testsuite-
QA Contact: general → build-config
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.0b2
Reporter | ||
Updated•15 years ago
|
Attachment #388913 -
Attachment is obsolete: true
Attachment #388913 -
Flags: review?(kairo)
Comment 13•15 years ago
|
||
Nice, we now have the same 484 leak than on the other boxes - at least that inconsistency on that one VM seems to be gone :)
You need to log in
before you can comment on or make changes to this bug.
Description
•