Changeset 205484 in webkit
- Timestamp:
- Sep 6, 2016 9:26:05 AM (8 years ago)
- Location:
- trunk/Source/WebKit2
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/Source/WebKit2/ChangeLog
r205475 r205484 1 2016-09-06 Carlos Garcia Campos <cgarcia@igalia.com> 2 3 [Threaded Compositor] Update timer should have lower priority than tasks scheduled in compositing thread 4 https://bugs.webkit.org/show_bug.cgi?id=161625 5 6 Reviewed by Sergio Villar Senin. 7 8 This way, if a resize is scheduled, for example, and there are pending updates, the resize will happen first, 9 and then the updates will happen at the right size. 10 11 * Shared/CoordinatedGraphics/threadedcompositor/CompositingRunLoop.cpp: 12 (WebKit::CompositingRunLoop::CompositingRunLoop): Use G_PRIORITY_HIGH_IDLE as update timer priority. The actual 13 priority doesn't really matter as long as it's lower than G_PRIORITY_DEFAULT, because there are only two 14 possible sources in the compositing run loop, one for the tasks scheduled, and another one for the update timer. 15 1 16 2016-09-06 Emanuele Aina <emanuele.aina@collabora.com> 2 17 -
trunk/Source/WebKit2/Shared/CoordinatedGraphics/threadedcompositor/CompositingRunLoop.cpp
r203721 r205484 33 33 #include <wtf/NeverDestroyed.h> 34 34 #include <wtf/WorkQueue.h> 35 36 #if USE(GLIB_EVENT_LOOP) 37 #include <glib.h> 38 #endif 35 39 36 40 namespace WebKit { … … 109 113 , m_updateFunction(WTFMove(updateFunction)) 110 114 { 115 #if USE(GLIB_EVENT_LOOP) 116 m_updateTimer.setPriority(G_PRIORITY_HIGH_IDLE); 117 #endif 111 118 } 112 119
Note: See TracChangeset
for help on using the changeset viewer.