http://aem1k.com/mona is much faster with accelerated canvas, but leaks memory
Categories
(Core :: Graphics: Canvas2D, enhancement)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
(Blocks 1 open bug, )
Details
Attachments
(1 file)
|
29.50 KB,
text/plain
|
Details |
enable accelerated canvas
Go to https://codepen.io/jaysalvat/pen/kazzOj
AR: demo is fast (as compared to unaccelerated canvas) but memory leaks
|
Reporter | |
Updated•3 years ago
|
|
|
Reporter | |
Comment 1•3 years ago
|
||
|
|
Reporter | |
Comment 2•3 years ago
|
||
|
||
Updated•3 years ago
|
|
|
Reporter | |
Comment 4•3 years ago
|
||
Hi Lee. With Nightly as of https://hg.mozilla.org/mozilla-central/rev/c59c06e50b89ab3772d032e6a2344abbd505fe0d , I can still repro this bug.
If I let the demo run, the memory very quickly reaches 1.3GB.
Should this bug be unduped ?
|
|
||
Comment 5•3 years ago
|
||
As noted elsewhere, I solved the main escalation of memory, and there is still going to be some expected memory hit from accelerated canvas left over, but it is bounded. I did not observe any unbounded memory usage with my fixes in place. I think rather than unduping all these bugs we should rather file a separate bug to address a specific testcase that easily shows where memory usage is still high (but separate from the unbounded memory usage that was happening before).
|
|
Reporter | |
Comment 6•3 years ago
|
||
Thanks for the explanantion. On taking a memory report, I see that the memory increase is in the webcontent process now, and mostly in heap-unclassified. (That is probably bug 1765026 )
So this bug is FIXED.
Description
•