Closed
Bug 458328
Opened 17 years ago
Closed 15 years ago
Memory leak during TopSite Test on http://www.flurl.com
Categories
(Core :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: cbook, Unassigned)
References
()
Details
(Keywords: memory-leak)
Attachments
(1 file)
|
3.24 KB,
text/plain
|
Details |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.3pre) Gecko/2008092317
Minefield/3.0.3pre
Found during the automated Global-500 Topsite Test on http://www.flurl.com
nsStringStats
=> mAllocCount: 776248
=> mReallocCount: 165609
=> mFreeCount: 776216 -- LEAKED 32 !!!
=> mShareCount: 817046
=> mAdoptCount: 110515
=> mAdoptFreeCount: 110515
0 TOTAL 23 4248 33846749 114 ( 5799.64 +/- 4824.47) 36965986 135 ( 2341.48 +/- 3983.16)
nsTraceRefcntImpl::DumpStatistics: 760 entries
Tomcat: This is a regression since 3.0 right? If so, could you mark it a regression and nominate as blocker?
|
Reporter | |
Updated•16 years ago
|
Blocks: sisyphus-tracking
No longer depends on: sisyphus-tracking
WFM on trunk
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•