Closed Bug 515659 Opened 17 years ago Closed 17 years ago

We don't handle the case where we run out of memory before we reach the soft limit properly

Categories

(Tamarin Graveyard :: Garbage Collection (mmGC), defect, P3)

x86
macOS
defect

Tracking

(Not tracked)

VERIFIED FIXED
flash10.1

People

(Reporter: treilly, Assigned: treilly)

References

Details

Attachments

(1 file)

We could set the soft limit to zero in this case, since its never gonna get hit anyways.
I'm not sure what this bug is for - better description needed. Still, targeting since it sounds important.
Flags: flashplayer-qrb?
Target Milestone: --- → flash10.1
Priority: -- → P3
Flags: flashplayer-qrb?
The bug here is that if we go from kMemNormal to kMemReserve we will immediately issue a kMemNormal if memory is below the soft limit, we should only issue the kMemNormal if memory grew past the soft limit. It should be as if the soft limit is ignored in this case and the normal rules for going back to kMemNormal apply
Attached patch fix — — Splinter Review
New semantics: we only go from kMemNormal from kMemSoftLimit if the current status is kMemSoftLimit. Additionally the means if we go from kMemNormal to kMemSoftLimit to kMemReserve we only go back to normal if we return memory from the peak, going below the soft limit won't do it.
Assignee: nobody → treilly
Status: NEW → ASSIGNED
Attachment #405324 - Flags: superreview?(lhansen)
Attachment #405324 - Flags: review?(apiira)
Attachment #405324 - Flags: superreview?(lhansen) → superreview+
Comment on attachment 405324 [details] [diff] [review] fix Anti sent me email with approval, apparently bugzilla is giving him permissions problems.
Attachment #405324 - Flags: review?(apiira)
change 2746
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: