Changeset 241925 in webkit
- Timestamp:
- Feb 21, 2019 5:51:32 PM (5 years ago)
- Location:
- trunk/Source/WebKit
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebKit/ChangeLog
r241924 r241925 1 2019-02-21 Tim Horton <timothy_horton@apple.com> 2 3 Turn a high-value UI-side-compositing assertion into a release assert 4 https://bugs.webkit.org/show_bug.cgi?id=194887 5 6 Reviewed by Simon Fraser. 7 8 * WebProcess/WebPage/RemoteLayerTree/PlatformCALayerRemote.cpp: 9 (WebKit::PlatformCALayerRemote::recursiveBuildTransaction): 10 There is absolutely no situation in which this assert should fire 11 if WebKit is behaving correctly, and it will basically always result 12 in a UI process crash (or at least confusion), so make it a release assert. 13 This would have saved us a lot of stress in bug 194845. 14 1 15 2019-02-21 Don Olmstead <don.olmstead@sony.com> 2 16 -
trunk/Source/WebKit/WebProcess/WebPage/RemoteLayerTree/PlatformCALayerRemote.cpp
r241899 r241925 169 169 { 170 170 ASSERT(!m_properties.backingStore || owner()); 171 ASSERT_WITH_SECURITY_IMPLICATION(&context == m_context);171 RELEASE_ASSERT_WITH_SECURITY_IMPLICATION(&context == m_context); 172 172 173 173 if (m_properties.backingStore && (!owner() || !owner()->platformCALayerDrawsContent())) {
Note: See TracChangeset
for help on using the changeset viewer.