Open Bug 739633 Opened 9 years ago Updated 6 years ago

Investigate if nsHtml5TreeOpExecutor should use other data structures than nsTArray

Categories

(Core :: DOM: HTML Parser, defect)

12 Branch
x86_64
Linux
defect
Not set
normal

Tracking

()

UNCONFIRMED

People

(Reporter: smaug, Unassigned)

Details

Currently nsTArray is used for example for nsHtml5TreeOperation objects.
If parser is interrupted often, we end up plenty of memmoves because of RemoveElementsAt.
Maybe some kind of list could work better, though one needs to find the last 
handled op fast...

I haven't profiled this yet, so marking this UNCONFIRMED.
Hello, I am new to Mozilla development and am looking to contribute to fulfill a CS data structures course project. Could I get this bug assigned to me and some guidance on resolving/investigating it?
Is this still something worth investigating, Olli?
Flags: needinfo?(bugs)
This would need a test case and profiling, but yes, I believe parser isn't still very effective in
array handling. Profiling might show up some other perf issues, possibly not this one.
Flags: needinfo?(bugs)
Which profiler do you recommend using?
Also can anyone give me a general explanation of how the nsHtml5TreeOpExecuter class is used and how it fits into the html parsing process?
Also can anyone give me a general explanation of how the nsHtml5TreeOpExecuter class is used and how it fits into the html parsing process?
You need to log in before you can comment on or make changes to this bug.