[Gnash-commit] [bug #35351] Regression: timers broken when framerate above 12

[Benjamin Wolsey]

Update of bug #35351 (project gnash):

             Assigned to:                    None => rsavoye                

    _______________________________________________________

Follow-up Comment #2:

You appear to have missed the point. It is not about the exact count, but
about the resolution. You'll see that the Flash player now outpaces Gnash by
about 4 to 1.

Framerate can vary depending on external factors like CPU load. Timers use the
system time. You've broken it so that a framerate of 13 makes the minimum
timer resolution 76ms instead of the expected 10. A function that's supposed
to be called every 20ms will only be called approximately every 80ms.

Also this was a testcase I produced in 5 minutes showing just one of the
side-effects of the change. I could write any number of others showing
different problems. Please fix.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?35351>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/