Bug 208145

Summary: Document / DOMWindow objects get leaked on CNN.com due to CSSTransitions
Product: WebKit Reporter: Chris Dumez <cdumez>
Component: CSSAssignee: Chris Dumez <cdumez>
Status: RESOLVED FIXED    
Severity: Normal CC: commit-queue, graouts, graouts, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 208069    
Attachments:
Description Flags
Patch none

Chris Dumez
Reported 2020-02-24 10:46:01 PST
Document / DOMWindow objects get leaked on CNN.com due to CSSTransitions.
Attachments
Patch (4.63 KB, patch)
2020-02-24 10:47 PST, Chris Dumez 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Chris Dumez
Comment 1 2020-02-24 10:47:08 PST
Created attachment 391556 [details] Patch
WebKit Commit Bot
Comment 2 2020-02-24 12:28:28 PST
Comment on attachment 391556 [details] Patch Clearing flags on attachment: 391556 Committed r257235: <https://trac.webkit.org/changeset/257235>
WebKit Commit Bot
Comment 3 2020-02-24 12:28:30 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 4 2020-02-24 12:29:16 PST
<rdar://problem/59735531>
Antoine Quint
Comment 5 2020-04-10 04:01:36 PDT
I'm having second thoughts about the change to WeakPtr<Element> for KeyframeEffect. Consider this code: const effect = new KeyframeEffect(document.createElement("div"), {}); What will hold the assigned target alive?
Note You need to log in before you can comment on or make changes to this bug.