[Webkit-unassigned] [Bug 30898] Browser crash by deeply nested elements
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Tue Nov 24 10:30:12 PST 2009
https://bugs.webkit.org/show_bug.cgi?id=30898
--- Comment #11 from Keith Kyzivat <kkyzivat at ovi.com> 2009-11-24 10:30:12 PST ---
I have a proposed patch that I've had done for a while now, was just trying to
think if there would be any better way to do it.
It caps the tree in the parser when parser adds a node, and also in Javascript
when a node is appended.
There is no memory consumption increase, but there is a hit in performance,
since depth of node to be added/appended to is calculated, for each add/append.
Since there is a performance hit, I added a build flag to turn it on, and
specify the maximum depth. Under standard desktop browsers with large max
stack size, this can be omitted, since the maximum depth is generally in the
hundreds of thousands. For low-memory devices, this is a bigger deal, and thus
they may configure webkit with --enable-domtree-maxdepth=<value>.
Patch coming shortly.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list