Bug 53703

Summary: Run script to classify the leaks output to show unique leaks
Product: WebKit Reporter: Simon Fraser (smfr) <simon.fraser>
Component: Tools / TestsAssignee: Nobody <webkit-unassigned>
Status: NEW    
Severity: Normal CC: abarth, aroben, ddkilzer, eric, joepeck
Priority: P2 Keywords: InRadar, ToolsHitList
Version: 528+ (Nightly build)   
Hardware: PC   
OS: OS X 10.5   
Attachments:
Description Flags
uniq-leaks tool none

Simon Fraser (smfr)
Reported 2011-02-03 12:05:01 PST
We need to keep a better eye on the leak output. One way to do this would be to run a script to classify the leaks, and count the number of unique leaks.
Attachments
uniq-leaks tool (2.55 KB, text/plain)
2011-02-03 12:12 PST, David Kilzer (:ddkilzer) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
David Kilzer (:ddkilzer)
Comment 1 2011-02-03 12:12:26 PST
Created attachment 81096 [details] uniq-leaks tool Here's a really basic uniq-leaks tool (written in 2009 in Perl) that attempts to uniq leaks output. It just needs to be hooked up to old-run-webkit-tests --leaks.
Adam Roben (:aroben)
Comment 2 2011-03-09 10:38:41 PST
I just posted a tool in bug 56028 that makes viewing leaks output easier. It's not really set up for use in an automated fashion, however.
Adam Roben (:aroben)
Comment 3 2011-03-21 09:55:09 PDT
Some more ideas: 1) Use the uniq-leaks tool attached to this bug to show the number of unique leaks in the run-webkit-tests --leaks output, and also put that output on build.webkit.org 2) Show more information about leaks that have WTF::fastMalloc in the stack. These are leaks of JSC/WebCore/WebKit objects, and it should be pretty easy to say which objects and how many of each kind are leaking.
Adam Roben (:aroben)
Comment 4 2011-05-26 11:45:58 PDT
<rdar://problem/9509332>
Note You need to log in before you can comment on or make changes to this bug.