Bug 121662
| Summary: | BitVector::OutOfLineBits is always reported as a leak | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Alexey Proskuryakov <ap> |
| Component: | Web Template Framework | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | andersca, benjamin, darin, fpizlo, kling, mrowe, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=208580 | ||
Alexey Proskuryakov
BitVector::m_bitsOrPointer stores a transmogrified OutOfLineBits pointer, so it's always reported as a leak:
m_bitsOrPointer = bitwise_cast<uintptr_t>(newOutOfLineBits) >> 1;
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Radar WebKit Bug Importer
<rdar://problem/35767785>
Alexey Proskuryakov
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.
Alexey Proskuryakov
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.
Alexey Proskuryakov
> I'm not seeing
I'm *now* seeing