On a Canvas testcase from bug 1920660, Nightly uses 2GB+ RAM in image cache while Chrome uses 600MB
Categories
(Core :: Graphics: ImageLib, enhancement)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
Details
Attachments
(3 files)
STR:
Run the testcase (zip file with images, html file) , maybe on a Win11 machine.
AR:
memory increase from ~6GB to 9.3 GB which then reduces to ~8GB and ramps up-and-down between 8GB and 9.3GB.
ER: Chrome uses 600MB RAM. Maybe something to do better here?
|
Reporter | |
Comment 1•2 months ago
|
||
|
|
Reporter | |
Comment 2•2 months ago
|
||
|
|
Reporter | |
Comment 3•2 months ago
|
||
Profile: https://share.firefox.dev/4eiqLcO
Profile with graphics preset logging: https://share.firefox.dev/3MZWnYN
Profile with memory tracking: https://share.firefox.dev/3THVYxU
|
|
Reporter | |
Comment 4•2 months ago
|
||
|
||
Comment 5•2 months ago
|
||
Thanks for the memory report and profiles.
From the memory report the memory is being used by unlocked decoded images. This means that they can discarded at any time, just nothing has triggered them to be discarded. I think the surface cache, which holds decoded images, is set to 2 GB. So this isn't too surprising. Do we want to try to purge these decoded images more aggressively? Or decrease the size of the surface cache?
Description
•