71260 2011-10-31 17:58:24 -0700 Leaks seen in RenderFlowThread::setRegionRangeForBox on Leaks bot 2011-11-06 14:27:40 -0800 1 1 1 Unclassified WebKit Layout and Rendering 528+ (Nightly build) All All RESOLVED FIXED http://build.webkit.org/LeaksViewer/?url=http%3A%2F%2Fbuild.webkit.org%2F%2Fresults%2FSnowLeopard%20Intel%20Leaks%2Fr98879%20(19849)%2F InRadar, MakingBotsRed P2 Normal --- 57312 1 aroben darin darin hyatt mihnea mitz simon.fraser webkit-bug-importer oldest_to_newest 493683 0 aroben 2011-10-31 17:58:24 -0700 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. 493684 1 webkit-bug-importer 2011-10-31 17:58:56 -0700 <rdar://problem/10374428> 496759 2 darin 2011-11-05 18:19:47 -0700 *** Bug 71620 has been marked as a duplicate of this bug. *** 496761 3 darin 2011-11-05 18:20:43 -0700 This is the same leak as 71259. *** This bug has been marked as a duplicate of bug 71259 *** 496763 4 aroben 2011-11-05 18:22:29 -0700 How are they the same? Bug 71259 is about leaks of RenderBoxRegionInfo objects, this bug is about leaks of RenderRegionRange objects. 496765 5 aroben 2011-11-05 18:23:18 -0700 I guess one of those objects could own the other… 496804 6 darin 2011-11-06 08:42:04 -0800 Adam’s right. This is not a duplicate. 496845 7 mihnea 2011-11-06 12:37:21 -0800 In function RenderFlowThread::removeRenderBoxRegionInfo, the RenderRegionRange* for box is removed from the map but not deleted. 496884 8 darin 2011-11-06 14:24:29 -0800 Yes, you can see the patch I already posted and got reviewed to fix this in bug 71620. 496885 9 darin 2011-11-06 14:27:40 -0800 Committed r99384: <http://trac.webkit.org/changeset/99384>