mirrors/weston
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

compositor: warn about insane repaint delay

Browse Source 
Make the sanity check more explicit and log a warning if it happens.

Small negative values are ok because it just means the compositor is
lagging behind, or more likely the user specified a too long repaint
window.

Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.co.uk>
Reviewed-By: Derek Foreman <derekf@osg.samsung.com>
Reviewed-by: Bryce Harrington <b.harrington@samsung.com>
This commit is contained in:
Pekka Paalanen 2015-03-19 12:27:29 +02:00
parent 0513a95a06
commit 8fd4de458e
1 changed files with 12 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/compositor.c
View File

@ -2412,8 +2412,18 @@ weston_output_finish_frame(struct weston_output *output,
msec = (refresh_nsec - timespec_to_nsec(&gone)) / 1000000; /* floor */ msec = (refresh_nsec - timespec_to_nsec(&gone)) / 1000000; /* floor */
msec -= compositor->repaint_msec; msec -= compositor->repaint_msec;
/* Also sanity check. */ if (msec < -1000 || msec > 1000) {
if (msec < 1 || msec > 1000) static bool warned;
if (!warned)
weston_log("Warning: computed repaint delay is "
"insane: %d msec\n", msec);
warned = true;
msec = 0;
}
if (msec < 1)
output_repaint_timer_handler(output); output_repaint_timer_handler(output);
else else
wl_event_source_timer_update(output->repaint_timer, msec); wl_event_source_timer_update(output->repaint_timer, msec);