Closed
Bug 41398
Opened 25 years ago
Closed 24 years ago
Flush memory cache on low-memory condition
Categories
(Core :: Networking: Cache, defect, P3)
Tracking
()
VERIFIED
FIXED
M18
People
(Reporter: warrensomebody, Assigned: rpotts)
References
Details
(Keywords: arch, Whiteboard: [nsbeta3-] [have fix])
Attachments
(1 file)
Now there's a way to register an nsIMemoryPressureObserver with nsIMemory (the
replacement for nsIAllocator). We should hook up the memory cache to this.
assigning and approving.
Assignee: gagan → neeti
Status: ASSIGNED → NEW
Whiteboard: [nsbeta3+]
Comment 3•24 years ago
|
||
We are doubtful if this will get fixed. Will mark so soon once triage is
complete.
Status: NEW → ASSIGNED
Comment 4•24 years ago
|
||
Marking nsbeta3-
Seamonkey wont use memory cache(per cache meeting) and we are overflowing with
work already.
Rick Potts, do you want to take this bug. I thought we decided Rick was going to
limit number of memcache entries. Maybe this could be done along with that.
Assignee: neeti → rpotts
Status: ASSIGNED → NEW
Whiteboard: [nsbeta3+] → [nsbeta3-]
Assignee | ||
Comment 5•24 years ago
|
||
I'm attaching a patch which makes the cache manager an observer of the
low-memory notifications...
Assignee | ||
Comment 6•24 years ago
|
||
Assignee | ||
Comment 7•24 years ago
|
||
just waiting for approval to check the fix in...
Whiteboard: [nsbeta3-] → [nsbeta3-] [have fix]
Assignee | ||
Comment 8•24 years ago
|
||
I've just checked the patch into the trunk (r=neeti)
Assignee | ||
Comment 9•24 years ago
|
||
I'm closing this out since the SeaMonkey branch does not use the memory cache...
So it doesn't make sense to check it into the branch.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•