RESOLVED DUPLICATE of bug 86436 86437
CodeBlock::RareData() wastes a lot of vector capacity 
https://bugs.webkit.org/show_bug.cgi?id=86437
Summary CodeBlock::RareData() wastes a lot of vector capacity
Simon Fraser (smfr)
Reported 2012-05-14 21:56:01 PDT
Data collected via bug 86281 show that a lot of vector capacity is wasted via the Vectors allocated here: 2232 vectors, 0.31KB used of 558.00KB, 557.69KB wasted at: 1 0x106979f55 WTF::Vector<JSC::InlineCallFrame, 4ul>::Vector() 2 0x106979625 WTF::Vector<JSC::InlineCallFrame, 4ul>::Vector() 3 0x1069795c4 WTF::SegmentedVector<JSC::InlineCallFrame, 4ul>::SegmentedVector() 4 0x106979465 WTF::SegmentedVector<JSC::InlineCallFrame, 4ul>::SegmentedVector() 5 0x106979319 JSC::CodeBlock::RareData::RareData() 2232 vectors, 17.44KB used of 558.00KB, 540.56KB wasted at: 1 0x106979e45 WTF::Vector<WTF::Vector<JSC::InlineCallFrame, 4ul>*, 32ul>::Vector() 2 0x106979645 WTF::Vector<WTF::Vector<JSC::InlineCallFrame, 4ul>*, 32ul>::Vector() 3 0x1069795d6 WTF::SegmentedVector<JSC::InlineCallFrame, 4ul>::SegmentedVector() 4 0x106979465 WTF::SegmentedVector<JSC::InlineCallFrame, 4ul>::SegmentedVector() 5 0x106979319 JSC::CodeBlock::RareData::RareData() 2232 vectors, 66.41KB used of 310.97KB, 244.56KB wasted at: 1 0x10697a185 WTF::Vector<JSC::LineInfo, 0ul>::Vector() 2 0x106979425 WTF::Vector<JSC::LineInfo, 0ul>::Vector() 3 0x1069792f9 JSC::CodeBlock::RareData::RareData() 4 0x106975bd5 JSC::CodeBlock::RareData::RareData() 5 0x106974214 JSC::CodeBlock::createRareDataIfNecessary() 2232 vectors, 486.60KB used of 692.79KB, 206.19KB wasted at: 1 0x10697a285 WTF::Vector<JSC::ExpressionRangeInfo, 0ul>::Vector() 2 0x106979405 WTF::Vector<JSC::ExpressionRangeInfo, 0ul>::Vector() 3 0x1069792e9 JSC::CodeBlock::RareData::RareData() 4 0x106975bd5 JSC::CodeBlock::RareData::RareData() 5 0x106974214 JSC::CodeBlock::createRareDataIfNecessary()
Attachments
Add attachment proposed patch, testcase, etc.
Filip Pizlo
Comment 1 2012-05-15 13:44:33 PDT
*** This bug has been marked as a duplicate of bug 86436 ***
Note You need to log in before you can comment on or make changes to this bug.