Closed
Bug 516699
Opened 15 years ago
Closed 15 years ago
Increase the interval between low-memory notifications
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| status1.9.2 | --- | beta1-fixed |
People
(Reporter: dougt, Assigned: dougt)
Details
Attachments
(1 file)
|
(deleted),
patch
|
vlad
:
review+
pavlov
:
approval1.9.2+
|
Details | Diff | Splinter Review |
When I landed Bug 475595, i left the interval between the time we would rebroadcast a low-memory notification as 100ms. Vlad suggested that we could increase this value:
>100ms seems really aggressive; I'd make that 1000ms if not more. If we're out
of memory we may be hitting some sort of swap, so it could well be longer than
100ms just due to swapping or whatever, and we'll end up doing a lot of
flushing here for probably no good reason.
We should investigate using 1s as the value.
Attachment #400805 -
Flags: review?(vladimir) → review+
|
Assignee | |
Comment 2•15 years ago
|
||
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Updated•15 years ago
|
Flags: blocking1.9.2?
|
||
Updated•15 years ago
|
Attachment #400805 -
Flags: approval1.9.2+
|
|
Assignee | |
Comment 3•15 years ago
|
||
Flags: blocking1.9.2?
|
||
Comment 4•15 years ago
|
||
could this have caused a Ts regression? it's in the range for bug 517915.
|
|
Assignee | |
Comment 5•15 years ago
|
||
Dietrich, this change was to reduce the amount of work we do in low memory situations - so, i do not think it could be part of the regression.
|
||
Updated•15 years ago
|
status1.9.2:
--- → beta1-fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•