121662 2013-09-20 01:00:12 -0700 BitVector::OutOfLineBits is always reported as a leak 2020-03-04 10:17:47 -0800 1 1 1 Unclassified WebKit Web Template Framework 528+ (Nightly build) Unspecified Unspecified NEW https://bugs.webkit.org/show_bug.cgi?id=208580 InRadar P2 Normal --- 1 ap webkit-unassigned andersca benjamin darin fpizlo kling mrowe webkit-bug-importer oldest_to_newest 931212 0 ap 2013-09-20 01:00:12 -0700 BitVector::m_bitsOrPointer stores a transmogrified OutOfLineBits pointer, so it's always reported as a leak: m_bitsOrPointer = bitwise_cast<uintptr_t>(newOutOfLineBits) >> 1; 1376243 1 webkit-bug-importer 2017-11-30 00:16:35 -0800 <rdar://problem/35767785> 1376244 2 ap 2017-11-30 00:22:57 -0800 Silenced the leak in <http://trac.webkit.org/r225321>. It still needs to be fixed, as it will continue to show up as a leak for client apps which don't use webkitpy for leaks detection. 1382757 3 ap 2017-12-18 08:39:43 -0800 I'm not seeing many leaks under BitVector::resizeOutOfLine too. I don't see any recent changes to this code, so perhaps that's just because I ran a more complete set of tests. Adding BitVector::resizeOutOfLine to _callstacks_to_exclude_from_leaks too. 1382762 4 ap 2017-12-18 09:07:14 -0800 > I'm not seeing I'm *now* seeing