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)

defect

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.
Umbrella bugs live in Component: other :-)

Gerv
Component: Browser-General → other
Reassigning. (Oops)

Gerv
Assignee: asadotzler → chofmann
QA Contact: jelwell → leger
Keywords: meta
leger is no longer @netscape. changing qa contact to component's default
QA Contact: leger → chofmann
Status: NEW → ASSIGNED
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
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
reassigning kandrot bugs.
Assignee: kandrot → dougt
Status: ASSIGNED → NEW
Target Milestone: mozilla1.0 → ---
Blocks: 98275
we should get some data on this both in terms of footprint as well as performance.
Keywords: helpwanted
Target Milestone: --- → Future
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 :-).
mass reassigning to nobody.
Assignee: dougt → nobody
7 years out, is this of any practical use?  AFAICT it's tracking nothing.
OS: Other → All
Hardware: Other → All
10 years since the original report. Any progress?
Maybe this bug could be interesting for MemShrink?
Otherwise maybe this could be marked as fixed.
I'm making an executive decision to close this bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.