https://bugs.kde.org/show_bug.cgi?id=339545

            Bug ID: 339545
           Summary: Ktimer can lag when it doesn't get scheduled
           Product: plasma
           Version: git master
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: widget-timer
          Assignee: plasma-bugs@kde.org
          Reporter: kdebugs@cneufeld.ca

I started a Ktimer 30 minutes while doing some work on my machine.  Due to
memory pressure, the desktop became entirely unresponsive for about 4 minutes. 
The clock stopped, the mouse pointer didn't work, and so on.  This happens
occasionally with the work I do.
When the desktop became useable again, the clock applet caught up, but the
ktimer one did not.  My timer expired about 4 minutes late.

Reproducible: Didn't try

Steps to Reproduce:
1. Start a timer running
2. Badly overcommit memory, leading to an unresponsive system while swapping is
occuring
3. When the desktop becomes responsive, note that the timer doesn't catch up.

Actual Results:  
The timer goes off late, apparently due to it missing ticks.

Expected Results:  
The timer should use wall-clock time to keep itself synchronized.

-- 
You are receiving this mail because:
You are watching all bug changes.