nsXULElement uses nsVoidArray for its children, which burns two words due to the nsVoidArray's vtable. We should use nsCheapVoidArray (which rjesup is moving to XPCOM and renaming nsSmallVoidArray) to save a word here.

Comment on attachment 53761 [details] [diff] [review] use nsCheapVoidArray instead of nsVoidArray in nsXULElement sr=jst

Comment on attachment 53761 [details] [diff] [review] use nsCheapVoidArray instead of nsVoidArray in nsXULElement r=brendan@mozilla.org

r=rjesup@wgate.com Note that this may or may not actually save us any space, depending on the allocation granularity and the previous/new size of nsXULElement (or subclasses thereof). I'm sure everyone here knows this, of course. Also, it probably cost will cost us space if it's common for nsXULElements to have more than 1 child. If the distribution is heavily weighted to 0 elements and 1 element isn't too much more frequent than the larger values, then nsVoidArray * is more appropriate for CPU use reasons. What's the distribution of children of nsXULElements?

Fix checked in.