Open Bug 559327 Opened 14 years ago Updated 3 years ago

[HTML5] HTML5 parser seems to alloc and dealloc a lot

Categories

(Core :: DOM: HTML Parser, defect, P5)

x86
All
defect

Tracking

()

People

(Reporter: smaug, Unassigned)

References

Details

Could we perhaps recycle some of the memory
nsHTML5TreeBuilder::startTokenization and nsHTML5Tokenizer::start()
reserve?

Memory allocation and deallocation shows up pretty high in the Shark profiles.

(Note, in my simple .innerHTML tests html5 parser is already faster than the old parser)
Is the parser startup the main allocation problem? I would have guessed nsHtml5StackNode and nsString.
Depends on: 497818, 499636
I could re-profile, but in my testcase (setting innerHTML to some simple string value) it was really those two methods mentioned in comment 0 which were causing most of the (de)allocation.
Priority: -- → P3

Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.

If you have reason to believe, this is wrong, please write a comment and ni :jstutte.

Severity: normal → S4
Priority: P3 → P5
You need to log in before you can comment on or make changes to this bug.