Changeset 207069 in webkit
- Timestamp:
- Oct 11, 2016 1:49:18 AM (8 years ago)
- Location:
- releases/WebKitGTK/webkit-2.14/Source/WebCore
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
releases/WebKitGTK/webkit-2.14/Source/WebCore/ChangeLog
r207068 r207069 1 2016-09-22 Zalan Bujtas <zalan@apple.com> 2 3 Replace redundant prepareForDestruction() call with RELEASE_ASSERT in Document::removedLastRef. 4 https://bugs.webkit.org/show_bug.cgi?id=162467 5 6 Reviewed by Chris Dumez. 7 8 Since r205786 fixed the root cause of webkit.org/b/159372, we no longer need the workaround. 9 Replace it with a RELEASE_ASSERT to ensure clean state. 10 11 No new tests, covered by existing test. 12 13 * dom/Document.cpp: 14 (WebCore::Document::removedLastRef): 15 1 16 2016-09-10 Chris Dumez <cdumez@apple.com> 2 17 -
releases/WebKitGTK/webkit-2.14/Source/WebCore/dom/Document.cpp
r207068 r207069 679 679 incrementReferencingNodeCount(); 680 680 681 prepareForDestruction();681 RELEASE_ASSERT(!hasLivingRenderTree()); 682 682 // We must make sure not to be retaining any of our children through 683 683 // these extra pointers or we will create a reference cycle.
Note: See TracChangeset
for help on using the changeset viewer.