Bug 18563

Summary: CSS Canvas leaks like a sieve
Product: WebKit Reporter: John Daggett <jdaggett>
Component: CSSAssignee: Dave Hyatt <hyatt>
Status: RESOLVED FIXED    
Severity: Major CC: hyatt
Priority: P1 Keywords: HasReduction
Version: 528+ (Nightly build)   
Hardware: Mac   
OS: OS X 10.4   
URL: http://people.mozilla.org/~jdaggett/webkitcanvascss2.html
Attachments:
Description Flags
sample dump from Activity Monitor
none
Learn2useOwnPtrProperly sam: review+

John Daggett
Reported 2008-04-17 19:43:17 PDT
While fiddling with the use of a canvas image in a css background, ran into a browser hang. Steps: 1. Load URL with latest nightly 2. Let run for a few minutes. Result: background goes away, only text shows and browser hangs (*not* a crash, just beach ball) In Activity Monitor, memory usage shows up at 3.55gb. Guessing some sort of mem leak. Process sample is attached.
Attachments
sample dump from Activity Monitor (5.34 KB, text/plain)
2008-04-17 19:46 PDT, John Daggett
no flags
Learn2useOwnPtrProperly (594 bytes, patch)
2008-04-17 21:01 PDT, Dave Hyatt
sam: review+
John Daggett
Comment 1 2008-04-17 19:46:06 PDT
Created attachment 20656 [details] sample dump from Activity Monitor
Matt Lilek
Comment 2 2008-04-17 20:38:27 PDT
Confirmed with r32016. This example leaks horribly for me. With MallocStackLogging turned on: 1. Started Safari with a blank home page (using ~19 MB RAM). 2. Let the testcase run for 30 seconds 3. Close the window; let it sit for 15 seconds (up to ~130 MB RAM) 4. Run leaks with the following output: Process 28694: 39259 nodes malloced for 5581 KB Process 28694: 1483 leaks for 130592 total leaked bytes.
Matt Lilek
Comment 3 2008-04-17 20:43:33 PDT
The entire leaks output is 6.5 MB which bugzilla doesn't like, so I've just uploaded the file to my webserver for now: <http://mattlilek.com/files/WebKitBug18563Leaks.txt>
Dave Hyatt
Comment 4 2008-04-17 21:01:38 PDT
Created attachment 20657 [details] Learn2useOwnPtrProperly
Dave Hyatt
Comment 5 2008-04-17 21:07:57 PDT
Fixed (in theory) in r32046.
Note You need to log in before you can comment on or make changes to this bug.