Closed
Bug 37445
Opened 24 years ago
Closed 13 years ago
service objects should be release ASAP to reduce footprint & memory leaks
Categories
(Core Graveyard :: Tracking, defect, P3)
Core Graveyard
Tracking
Tracking
(Not tracked)
RESOLVED
WONTFIX
Future
People
(Reporter: yueheng.xu, Unassigned)
References
()
Details
(Keywords: helpwanted, meta)
This is an umbrella bug report to request XPCOM module callers to release service objects ASAP to reduce the memory foot print and possible memory leaks. You can add your comments here if you see one whose speed performance outweights the memory footprint and the risks of memory leaks.
Comment 1•24 years ago
|
||
Umbrella bugs live in Component: other :-) Gerv
Component: Browser-General → other
Comment 2•24 years ago
|
||
Reassigning. (Oops) Gerv
Assignee: asadotzler → chofmann
QA Contact: jelwell → leger
Comment 3•24 years ago
|
||
leger is no longer @netscape. changing qa contact to component's default
QA Contact: leger → chofmann
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 4•23 years ago
|
||
kandrot, something to check up on, or toss the bug into the invalid bin if it doesn't seem usefull...
Assignee: chofmann → kandrot
Status: ASSIGNED → NEW
Comment 5•23 years ago
|
||
I will look into this and see if there is a win to be had here. I will research the problem first, since the initial text description does not currently mean anything to me. If this is not an umbrella bug, I will need a specific example. If it is an umbrella bug, then it will probably be an ongoing process, part of the design phase, not the bug fixing phase.
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.0
Comment 6•23 years ago
|
||
reassigning kandrot bugs.
Assignee: kandrot → dougt
Status: ASSIGNED → NEW
Target Milestone: mozilla1.0 → ---
Comment 7•23 years ago
|
||
we should get some data on this both in terms of footprint as well as performance.
Keywords: helpwanted
Target Milestone: --- → Future
Comment 8•23 years ago
|
||
There's another approach here... you can also use the memory pressure observation (http://lxr.mozilla.org/seamonkey/source/xpcom/base/nsIMemory.idl#60) technique and clean up when told to. Of course, this assumes appropriate firing of the pressure topic :-).
Comment 10•16 years ago
|
||
7 years out, is this of any practical use? AFAICT it's tracking nothing.
Comment 11•14 years ago
|
||
10 years since the original report. Any progress?
Comment 12•13 years ago
|
||
Maybe this bug could be interesting for MemShrink? Otherwise maybe this could be marked as fixed.
Comment 13•13 years ago
|
||
I'm making an executive decision to close this bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•