98234 2012-10-02 23:14:54 -0700 HTMLFormElement::m_elementAliases might cause a leak 2017-06-16 19:12:03 -0700 1 1 1 Unclassified WebKit New Bugs 528+ (Nightly build) Unspecified Unspecified RESOLVED CONFIGURATION CHANGED P2 Normal --- 1 webkit.review.bot abarth abarth deepak.deepakmittal joepeck oldest_to_newest 733378 0 webkit.review.bot 2012-10-02 23:14:54 -0700 HTMLFormElement::m_elementAliases might cause a leak Requested by abarth on #webkit. 733381 1 abarth 2012-10-02 23:16:50 -0700 From inspecting the code, it looks like the following will cause HTMLFormElement::m_elementAliases to hold a RefPtr to a parent of the form element. 1) Get a form element by name (so that the form element is stored in m_elementAliases). 2) Reparent the <form> under that element Note: I haven't actually tested this issue. It likely can be fixed by clearing m_elementAliases when HTMLFormElement is moved. 733382 2 abarth 2012-10-02 23:19:56 -0700 11:15 PM <othermaciej> There's also I think an attribute to explicitly make a form association, rather than implicitly; not sure if that could also cause the problem 11:15 PM <othermaciej> the form="" attribute 11:16 PM <othermaciej> it looks like <object> will respect the form="" attribute in our implementation, which may be a bug 11:17 PM <othermaciej> nope, correct per spec 11:17 PM <othermaciej> an <object>, <textarea> or <select> could be the ancestor of its associated form just in markup, w/o reparenting 733383 3 abarth 2012-10-02 23:20:45 -0700 11:19 PM <othermaciej> oh, I guess <object> is not an HTMLFormConrolElement so can't be in the alias map 974913 4 deepak.deepakmittal 2014-02-02 21:04:56 -0800 I am not able to find m_elementAliases in HTMLFormElement.cpp/h files, I think the code has been changed the issue has been filed.. please check the issue on the latest code..so that we can work on this or close this issue.. Deepak Mittal 1320296 5 joepeck 2017-06-16 19:12:03 -0700 Yep, this member no longer exists. Closing.