Closed Bug 1031926 Opened 11 years ago Closed 11 years ago

Parse sprites lazily

Categories

(Firefox Graveyard :: Shumway, defect)

Product:
Firefox Graveyard
Component:
Shumway
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1035170

People

(Reporter: till, Assigned: tschneider)

References

Details

(Whiteboard: [parser][memory usage][performance])

Same idea as in bug 1031925, but for defineSprite. In this case, we could even parse the sprite's frames as we go. To reduce average memory usage, it might make sense to not have all frames in one buffer, but multiple buffers with, say, 50 or 100 frames each. We could then get rid of the buffers we don't need anymore. Alternatively, we could consider re-lazifying frames or only decoding them temporarily for applying them and not storing the results at all. Might well be that the overhead for that is insignificant. @tobytailor, again your thoughts would be highly appreciated.
Blocks: 1035170
Assignee: nobody → schneider
Status: NEW → ASSIGNED
No longer blocks: shumway-m4
I made all parsing lazy in bug 1035170.
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.