• jbauman's avatar
    Process pending delayed tasks in kMsgHaveWork · 9316d3b9
    jbauman authored
    With 1 win32 timer we can only get a callback every 10ms, and since the callback only processes one message, that means the queue could keep growing if delayed tasks are posted faster than that rate, even if they're processed very quickly. To prevent that, schedule a kMsgHaveWork if there's 0ms until the next delayed task should run, and run a delayed task in the kMsgHaveWork handler.
    
    BUG=454333
    TEST=chrome resizes smoothly
    
    Review URL: https://codereview.chromium.org/918473002
    
    Cr-Commit-Position: refs/heads/master@{#330816}
    9316d3b9
message_pump_win.h 13.1 KB