Open
Bug 996512
Opened 11 years ago
Updated 2 years ago
Do not store local image source in memory
Categories
(Core :: Graphics: ImageLib, defect, P3)
Tracking
()
NEW
tracking-b2g | backlog |
People
(Reporter: kanru, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [c=memory p= s= u=tarako] [MemShrink:P3][demo])
Attachments
(7 files)
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review | |
(deleted),
patch
|
Details | Diff | Splinter Review |
+++ This bug was initially created as a clone of Bug #983050 +++
If the image is a local resource (resource://, file://, jar://, blob://, etc) we know we could read it back anytime so don't need to store the image source data for decode-on-draw or discardable surface.
We could mark if the resource is local when creating a request and add a method to imgIContainer to re-request image data when needed.
Whiteboard: [c=memory p= s= u=tarako] [MemShrink:P2][demo] → [c=memory p= s= u=tarako] [MemShrink][demo]
Updated•11 years ago
|
blocking-b2g: --- → 1.3T?
We might take this if we have data to prove this helps with performance. Placing in backlog.
blocking-b2g: 1.3T? → backlog
Comment 2•11 years ago
|
||
app:// works too
Not sure for blob: because it can be revoked.
Comment 3•11 years ago
|
||
app:// could be especially important because nearly all our image data comes from this scheme...
Comment 4•11 years ago
|
||
We could keep a reference of blob in cache. Is it work?
Comment 5•11 years ago
|
||
note that the discussion in [1] is definitely related.
[1] https://groups.google.com/forum/#!topic/mozilla.dev.b2g/81lxhZQgevM
Updated•11 years ago
|
Whiteboard: [c=memory p= s= u=tarako] [MemShrink][demo] → [c=memory p= s= u=tarako] [MemShrink:P3][demo]
Updated•11 years ago
|
Priority: -- → P3
Reporter | ||
Updated•11 years ago
|
Assignee: nobody → kchen
Updated•11 years ago
|
blocking-b2g: backlog → 1.3T?
Reporter | ||
Comment 7•11 years ago
|
||
Reporter | ||
Comment 8•11 years ago
|
||
Reporter | ||
Comment 9•11 years ago
|
||
Reporter | ||
Comment 10•11 years ago
|
||
Reporter | ||
Comment 11•11 years ago
|
||
Reporter | ||
Comment 12•11 years ago
|
||
Reporter | ||
Comment 13•11 years ago
|
||
Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Reporter | ||
Updated•10 years ago
|
Assignee: kchen → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•