Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.14.2, 5.15.0
-
None
-
5
-
0180a1ab8229c6a15d19317bf7680663ac402910 (qt/qtbase/dev) 95d3fe5afa016410580fb995044cf1145c03470a (qt/tqtc-qtbase/tqtc/lts-5.15) 27cde011277b18e06de75b3369c4a13451e6c3b0 (qt/qtbase/6.0)
-
Qt6_Foundation_Sprint 23, Qt6_Foundation_Sprint 24, Qt6_Foundation_Sprint 25, Qt6_Foundation_Sprint 26
Description
QCalendar class uses its internal containers shared across the class, such as Registry::byId and Registry::byName. But the access to those containers is not protected from multi-thread access. As a result, despite the document's "all functions in this class are reentrant" statement, this class can be used safely only form one thread.
Attachments
Issue Links
- is duplicated by
-
QTBUG-85692 Race in QTime::toString
- Closed
-
QTBUG-88815 QDate::FromString breaks when accessed from multiple threads using default calendar parameter
- Closed
- relates to
-
QTBUG-93004 Assert and crash in qcalendar.cpp when the first call to QDateTime::toString is done from two simultaneous threads
- Closed
For Gerrit Dashboard: QTBUG-84575 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
309227,2 | Add QMutex to fix race condition in QCalendar | dev | qt/qtbase | Status: ABANDONED | 0 | 0 |
309280,2 | QCalendar: protect the registry from concurrent access | dev | qt/qtbase | Status: ABANDONED | +2 | 0 |
309673,14 | Make QCalendar's backend registration reentrant-safe | dev | qt/qtbase | Status: MERGED | +2 | 0 |
316326,2 | Protect the calendar registry methods from use during destruction | dev | qt/qtbase | Status: ABANDONED | -1 | 0 |
331253,2 | Make QCalendar's backend registration reentrant-safe | 6.0 | qt/qtbase | Status: MERGED | +2 | 0 |
331255,2 | Make QCalendar's backend registration reentrant-safe | tqtc/lts-5.15 | qt/tqtc-qtbase | Status: MERGED | +2 | 0 |