583186 - Massive memory leak when rerendering canvas (reproducible)

Status: RESOLVED WORKSFORME

(Core :: Graphics: Canvas2D, defect)

Description

[Jaroslav Benc]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b2) Gecko/20100720 Firefox/4.0b2

Example code: 

document.addEventListener("mousemove", function(ev){
   canvas.width = 500;
   ctx.fillStyle = "rgb(40,0,0)";
   ctx.fillRect (0, 0, ev.clientX, ev.clientY);
}, false);

Reproducible: Always

Steps to Reproduce:
1. create a canvas element and use the code above
2. open your task manager and see firefox memory when moving mouse

Actual Results:  
Memory grows quickly so you can get 1.8GB after less than 1 minute of mousemove

Expected Results:  
Shouldn't leak as FF 3.6

Applies to FF4, both betas

Comment 1

[Jaroslav Benc]

Attachment: example of the memory leak - move mouse and see you taskbar

Comment 2

[(mostly gone) XtC4UaLL [:xtc4uall]]

Using Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b3pre) Gecko/20100730 Minefield/4.0b3pre ID:20100730040228 there's normal Memory Behavior visible for me (~45,x MB (Private Bytes) with the Testcace as the only Tab), CPU Time is spiking of course.

Can you reproduce you Issue using a recent Trunk Build?
(http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/)

Comment 3

[Jaroslav Benc]

Can't reproduce this bug anymore using the 4.0b3pre build so it has been fixed recently.

Comment 4

[Wladimir Palant]

Works for me in Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7pre) Gecko/20100915 Firefox/4.0b7pre, resolving since the reporter cannot reproduce it either.