aw-android icon indicating copy to clipboard operation
aw-android copied to clipboard

Stopwatch continues running after stopped

Open lerad opened this issue 3 years ago • 2 comments

I have encountered a bug in the "Stopwatch" feature. It sometimes restarts a stopwatch, after I already stopped it.

I assume that this happens when the view is closed/terminated, before the "stop event" (or whatever the correct term is) is sent to the rust-backend. The best method I found to reproduce is:

  • Start a stopwatch
  • Let the stopwatch run for some time
  • Stop the stopwatch
  • Close the view manually, by using the "overview" button of the phone and closing the app
  • Re-open activitywatch
  • The stopwatch runs again

This does not trigger the bug 100%, so I would assume that there is some racing condition or the operation takes some time. My assumptions would have been that after pressing stop, the termination is directly "committed", but this does not seem to be the case. The bug also happens, when I don't close the view manually, just by switching to another app.

ActivityWatch: v.0.10.0 (rust) (Installed over Google playstore) Android: 8.0.0 (Samsung Galaxy S7)

lerad avatar Feb 03 '22 18:02 lerad

Still an issue. It just continues to run the last stopwatch. There are two faulty scenarios: Steps:

  1. start 1st stopwatch
  2. stop 1st stopwatch
  3. start 2nd stopwatch
  4. stop 2nd stopwatch
  5. close the app
  6. reopen the app

Result: 2nd stopwatch keeps running

Steps:

  1. start 1st stopwatch
  2. stop 1st stopwatch
  3. start 2nd stopwatch
  4. stop 2nd stopwatch
  5. remove 2nd stopwatch
  6. close the app
  7. reopen the app

Result: 1st stopwatch keeps running

wojnilowicz avatar Mar 14 '24 18:03 wojnilowicz

Setting battery usage of ActivityWatch to Unrestricted makes this issue go away.

wojnilowicz avatar Mar 21 '24 16:03 wojnilowicz