RESOLVED FIXED 71260
Leaks seen in RenderFlowThread::setRegionRangeForBox on Leaks bot 
https://bugs.webkit.org/show_bug.cgi?id=71260
Summary Leaks seen in RenderFlowThread::setRegionRangeForBox on Leaks bot
Adam Roben (:aroben)
Reported 2011-10-31 17:58:24 PDT
http://build.webkit.org/LeaksViewer/?url=http%3A%2F%2Fbuild.webkit.org%2F%2Fresults%2FSnowLeopard%20Intel%20Leaks%2Fr98879%20(19849)%2F malloc_zone_malloc > malloc > fastMalloc > RenderFlowThread::setRegionRangeForBox We're leaking in this function. Looks like we're allocating a new RenderRegionRange, storing it in a HashMap, and never deleting it.
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2011-10-31 17:58:56 PDT
<rdar://problem/10374428>
Darin Adler
Comment 2 2011-11-05 18:19:47 PDT
*** Bug 71620 has been marked as a duplicate of this bug. ***
Darin Adler
Comment 3 2011-11-05 18:20:43 PDT
This is the same leak as 71259. *** This bug has been marked as a duplicate of bug 71259 ***
Adam Roben (:aroben)
Comment 4 2011-11-05 18:22:29 PDT
How are they the same? Bug 71259 is about leaks of RenderBoxRegionInfo objects, this bug is about leaks of RenderRegionRange objects.
Adam Roben (:aroben)
Comment 5 2011-11-05 18:23:18 PDT
I guess one of those objects could own the other…
Darin Adler
Comment 6 2011-11-06 08:42:04 PST
Adam’s right. This is not a duplicate.
Mihnea Ovidenie
Comment 7 2011-11-06 12:37:21 PST
In function RenderFlowThread::removeRenderBoxRegionInfo, the RenderRegionRange* for box is removed from the map but not deleted.
Darin Adler
Comment 8 2011-11-06 14:24:29 PST
Yes, you can see the patch I already posted and got reviewed to fix this in bug 71620.
Darin Adler
Comment 9 2011-11-06 14:27:40 PST
Committed r99384: <http://trac.webkit.org/changeset/99384>
Note You need to log in before you can comment on or make changes to this bug.