126049 2013-12-19 21:47:01 -0800 Remove a significant source of memory allocations during CSS parsing 2016-04-29 09:20:35 -0700 1 1 1 Unclassified WebKit CSS 528+ (Nightly build) Unspecified Unspecified RESOLVED DUPLICATE 140599 BlinkMergeCandidate P2 Normal --- 1 rniwa webkit-unassigned barraclough benjamin cdumez joepeck kling koivisto oldest_to_newest 961732 0 rniwa 2013-12-19 21:47:01 -0800 Consider merging https://chromium.googlesource.com/chromium/blink/+/3d1744e53a3540be9bdb385deadec60469e6019c or come up with a similar improvement This is about +2% on Parser/css-parser-yui.html locally. Previously, we were allocating and freeing small vector buffers (most commonly 24 or 72 byte allocations on 64-bit), only to immediately throw them away. Note that uncheckedAppend has an ASSERT that will cleanly catch any future problems with sizing. 1188449 1 joepeck 2016-04-28 17:11:20 -0700 Still worth taking? Seems like a pretty small change, but might be out of date now. 1188636 2 cdumez 2016-04-29 09:20:35 -0700 I don't believe this is still needed after: https://bugs.webkit.org/show_bug.cgi?id=140599 *** This bug has been marked as a duplicate of bug 140599 ***