If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

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

NEW
Unassigned

Status

()

Core
HTML: Parser
P3
normal
8 years ago
2 years ago

People

(Reporter: smaug, Unassigned)

Tracking

(Depends on: 1 bug)

Trunk
x86
All
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
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
(Reporter)

Comment 2

8 years ago
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
You need to log in before you can comment on or make changes to this bug.