Closed Bug 46709 Opened 24 years ago Closed 24 years ago

xpcom component registry memory usage

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Platform:
All
Other
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 46832

People

(Reporter: warrensomebody, Assigned: waterson)

Details

(Keywords: memory-footprint)

From the footprint meeting 7/26/00: 8) Component registry loading Description: We load and inflate the component registry at startup time. We've heard anecdotally that the in-memory cost of the component registry is 1-3 megs. This hit could become worse if/when we implement RayW's new scheme for prog IDs. Need to see if we can use a better scheme to reduce bloat. Module owner: rayw@netscape.com Task owner: waterson@netscape.com, dougt@netscape.com Status: Chris and Doug to do analysis of memory usage so we have real numbers.
Keywords: footprint, nsbeta3
*** This bug has been marked as a duplicate of 46832 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
marking Verified as a dup.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.