-
Bug
-
Resolution: Fixed
-
P1: Critical
-
6.5, 6.7
-
None
-
Windows
-
66a76da0a (dev), 21e9875d6 (dev), 701263379 (6.8), 7e5f80ebb (tqtc/lts-6.5)
-
Foundation Sprint 116, Foundation Sprint 117
QObject::timerEvent may be called before the timer elapsed because timer ids are aggressively reused by Qt's timers. This issue can happen if
- A timer was recently stopped
- There are remaining WM_TIMER events in the Windows event queue
- QObject::startTimer is used to create a new timer
Under these conditions, QObject::startTimer will likely reuse the timer id of the previously stopped timer. This causes premature execution of QObject::timerEvent when the lingering WM_TIMER is processed.
This can for example cause premature false return from QSignalSpy even if no signals were received, which leads to flaky tests.
See also
- is duplicated by
-
QTBUG-132926 Guard WinTimerInfo::obj with a QPointer
-
- Closed
-
- relates to
-
-
- Open
-
-
-
- Closed
-
- resulted in
-
-
- Closed
-
| For Gerrit Dashboard: QTBUG-124496 | ||||||
|---|---|---|---|---|---|---|
| # | Subject | Branch | Project | Status | CR | V |
| 555771,2 | [Windows] Prevent premature timer events caused lingering timer messages | dev | qt/qtbase | Status: ABANDONED | -1 | 0 |
| 564638,5 | Add test that demonstrates premature timer events on Windows | dev | qt/qtbase | Status: MERGED | +2 | +1 |
| 582239,10 | QFreeList: return timer IDs with the serial included | dev | qt/qtbase | Status: MERGED | +2 | +1 |
| 597305,3 | QFreeList: return timer IDs with the serial included | 6.8 | qt/qtbase | Status: MERGED | +2 | 0 |
| 598479,2 | QFreeList: return timer IDs with the serial included | tqtc/lts-6.5 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |