Open
Bug 1042393
Opened 10 years ago
Updated 2 years ago
Allow expiration and unloading of background-images
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
tracking-b2g | backlog |
People
(Reporter: khuey, Unassigned)
References
Details
(Whiteboard: [MemShrink:P2])
Right now once a selector matches the image is loaded and remains in memory until the style sheet is destroyed. This leads to wasting a lot of memory when background-image is used for seldom-used images in long-lived things, such as the b2g system app.
Updated•10 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P2]
Comment 1•10 years ago
|
||
[Blocking Requested - why for this release]:
Blocking a blocker
blocking-b2g: --- → 2.0?
Comment 2•10 years ago
|
||
Lets get an owner for this ASAP. Is this a fix we can make in Gaia or do we need Gecko (DOM?) help here?
Updated•10 years ago
|
blocking-b2g: 2.0? → 2.0+
Reporter | ||
Comment 4•10 years ago
|
||
I think we should unblock on this for two reasons.
1. The patch is relatively risky. I have a proof of concept locally but it still has crashes that I don't understand yet. I worry that this is going to be too risky for this point in the 2.0 cycle.
2. The upside of this is limited. After using the phone for several hours the amount of compressed image data stored in memory is less than 1 MB. We got rid of the biggest offenders in Bug 1039631. Everything else is pretty tiny.
I don't think the risk we would be adding with this is worth less than 1 MB.
blocking-b2g: 2.0+ → 2.0?
Reporter | ||
Comment 7•10 years ago
|
||
Yes. I have a patch but it has some issues, and I keep getting sidetracked by higher priority stuff.
Flags: needinfo?(khuey)
Assignee | ||
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Reporter | ||
Updated•8 years ago
|
Assignee: khuey → 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
•