[Webkit-unassigned] [Bug 39621] Extreme memory growth on DOM Hanoi test
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon May 24 14:54:03 PDT 2010
https://bugs.webkit.org/show_bug.cgi?id=39621
--- Comment #1 from Alexey Proskuryakov <ap at webkit.org> 2010-05-24 14:54:02 PST ---
One thing I'm seeing is the same as <https://bugs.webkit.org/show_bug.cgi?id=9880> - we just added a notification that's sent to the client when form controls change:
HTMLTextAreaElement::HTMLTextAreaElement(const QualifiedName& tagName, Document* document, HTMLFormElement* form)
<...>
{
ASSERT(hasTagName(textareaTag));
setFormControlValueMatchesRenderer(true);
notifyFormStateChanged(this); // <-- here an ObjC wrapper for the node is created and autoreleased
}
It's more tricky to fix, because HTML elements start with refcount zero, so draining the autorelease pool would destroy HTMLTextAreaElement - during its own constructor!
The offending notifyFormStateChanged() call was added in <http://trac.webkit.org/changeset/39152>. It's only present for HTMLTextArea, which makes me wonder if it's actually needed.
--
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