Summary: | Fix XMLHttpRequest leak document when send() is called multiple times | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ryosuke Niwa <rniwa> |
Component: | XML | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED INVALID | ||
Severity: | Normal | CC: | aestes, allan.jensen, ap, darin, mrowe |
Priority: | P2 | Keywords: | BlinkMergeCandidate, InRadar |
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Ryosuke Niwa
2013-08-29 20:44:10 PDT
*** Bug 120886 has been marked as a duplicate of this bug. *** WebKit doesn't have this leak, it was introduced in Blink after forking. I'm not super eager to merge just the tests, as leak tests seems to generally not be worth the cost, due to being unreliable. > XMLHttpRequest::stop() still uses asynchronous unsetPendingActivity() to workaround issues mentioned in r152266. This refers to <https://chromiumcodereview.appspot.com/16284009>. Darin has fixed those issues in a better way in <http://trac.webkit.org/changeset/167579>. (In reply to comment #3) > I'm not super eager to merge just the tests, as leak tests seems to > generally not be worth the cost, due to being unreliable. I agree with everything else, but I don’t agree with this! My theory is that we think of leak tests as unreliable right now because we have so many unfixed leaks. I think that it's also about timing dependence due to garbage collection, and often relying on additional hooks. |