Bug #7682

Replace OrientationRestorer TimerTask usage with ScheduledExecutor

Added by Jani Simomaa about 1 month ago. Updated 10 days ago.

Status:ClosedStart date:2017-12-14
Priority:4Due date:2017-12-14
Assignee:Jani Simomaa% Done:

100%

Category:-Spent time:-
Target version:2017-28
Release notes:Replace use of @Timer@ and @TimerTask@ with @ScheduledExecutor@ in G2D @OrientationRestorer@ to prevent the system from piling up timer task executions while the machine is sleeping.
Tags: 1.32.0
Story points-
Velocity based estimate-
ReleaseSimantics 1.32.0Release relationshipAuto

Associated revisions

Revision 5998374f
Added by Jani Simomaa about 1 month ago

Replace OrientationRestorer TimerTask usage with ScheduledExecutor

Timer can exhaust the system with TimerTask-runnables that are queued up
e.g. during computer hibernate and sleep. According to documentation:

If an execution is delayed for any reason (such as garbage collection or
other background activity), two or more executions will occur in rapid
succession to "catch up." In the long run, the frequency of execution
will be exactly the reciprocal of the specified period

With heavy tasks this is very bad

refs #7682

Change-Id: I5a097c8bc5e1ea2a5abe30905b2a46fa8b8386f8

History

#1 Updated by Tuukka Lehtonen 10 days ago

  • Target version changed from 2017-27 to 2017-28

#2 Updated by Tuukka Lehtonen 10 days ago

  • Tags set to 1.32.0
  • Status changed from New to Closed
  • % Done changed from 0 to 100
  • Release set to 57
  • Release notes set to Replace use of @Timer@ and @TimerTask@ with @ScheduledExecutor@ in G2D @OrientationRestorer@ to prevent the system from piling up timer task executions while the machine is sleeping.

Also available in: Atom PDF