Changeset 215557 in webkit
- Timestamp:
- Apr 20, 2017, 5:57:40 AM (8 years ago)
- Location:
- trunk/Source/WebCore
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebCore/ChangeLog
r215555 r215557 1 2017-04-20 Antti Koivisto <antti@apple.com> 2 3 Increase large animation cutoff 4 https://bugs.webkit.org/show_bug.cgi?id=171051 5 <rdar://problem/31731532> 6 7 Reviewed by Andreas Kling. 8 9 We currently switch to per-frame decoding if the animation is larger than 5MB. This is very 10 power-inefficient and such animations are now common. The cutoff originates from 2007 (r20069), 11 it is time update it. 12 13 Note that the normal low memory handling will still kill animation frames as needed. 14 15 * platform/graphics/BitmapImage.h: 16 17 Increase cutoff to 30MB. This is enough (with some room to spare) for animations on current 18 tumblr.com/search/aww. 19 20 Also remove the separate cutoff value for iOS. 21 1 22 2017-04-20 Zan Dobersek <zdobersek@igalia.com> 2 23 -
trunk/Source/WebCore/platform/graphics/BitmapImage.h
r215211 r215557 196 196 197 197 // Animated images over a certain size are considered large enough that we'll only hang on to one frame at a time. 198 #if !PLATFORM(IOS) 199 static const unsigned LargeAnimationCutoff = 5242880; 200 #else 201 static const unsigned LargeAnimationCutoff = 2097152; 202 #endif 198 static const unsigned LargeAnimationCutoff = 30 * 1014 * 1024; 203 199 204 200 mutable ImageSource m_source;
Note:
See TracChangeset
for help on using the changeset viewer.