Huh that's weird. It actually shows the correct 336h for a few milliseconds first and then counts back from 35h. I wonder what's happening internally - messing up a timer shouldn't be that easy normally, right?
Looks like losing the hundreds digit of hours-- truncation.
Because windows search is useless and if I search "timer" it'll probably bring up "timer.py" from a random application or just search bing
It's odd. At first it shows is 336 hours, 0 mins, and 0 seconds and then it counts down to 35:59:59. Clearly a bug.