Closed
Bug 980037
Opened 11 years ago
Closed 11 years ago
Store scaled images in volatile buffers
Categories
(Core :: Graphics: ImageLib, defect)
Core
Graphics: ImageLib
Tracking
()
Tracking | Status | |
---|---|---|
b2g-v1.3T | --- | fixed |
People
(Reporter: mwu, Assigned: mwu)
References
Details
Attachments
(2 files)
10.70 KB,
patch
|
seth
:
review+
|
Details | Diff | Splinter Review |
10.67 KB,
patch
|
Details | Diff | Splinter Review |
No description provided.
Attachment #8386316 -
Flags: review?(seth)
Assignee | ||
Updated•11 years ago
|
blocking-b2g: --- → 1.3T?
Comment 1•11 years ago
|
||
Hi Michael, do you have any idea how much RAM/perf will be improved by this? thanks.
Flags: needinfo?(mwu)
Updated•11 years ago
|
Assignee: nobody → mwu
blocking-b2g: 1.3T? → 1.3+
Comment 2•11 years ago
|
||
Why was this marked 1.3+? Was that by accident or intentional?
Flags: needinfo?(fabrice)
Comment 3•11 years ago
|
||
Comment on attachment 8386316 [details] [diff] [review]
Store scaled images in volatile buffers
Review of attachment 8386316 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good.
Attachment #8386316 -
Flags: review?(seth) → review+
Assignee | ||
Comment 5•11 years ago
|
||
(In reply to Steven Yang [:styang] from comment #1)
> Hi Michael, do you have any idea how much RAM/perf will be improved by this?
> thanks.
This one primarily affects websites where we scale larger images down to fit the screen. It allows the scaled down version to also be thrown away under memory pressure. It's basically an improvement on bug 962670. I don't expect it to help as much as bug 962670, but it should have similar effects when we do generate scaled down images.
Flags: needinfo?(mwu)
Assignee | ||
Comment 6•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla30
Assignee | ||
Comment 8•11 years ago
|
||
Here's a v1.3t version of the patch.
Comment 9•11 years ago
|
||
status-b2g-v1.3T:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•