Details
-
Bug
-
Resolution: Done
-
P2: Important
-
6.2.0 Beta3
-
None
-
Linux QEMU armv7 GCC
-
ba8d1da4a971a6351318e86fc613f74843bb2c49 (qt/qtbase/dev) b9be95b070dc1580649aac94d48ff3ef8e391fbc (qt/qtbase/6.1) afd09834ce0f23088a7fe26e1518a058d080e70e (qt/qtbase/6.2)
Description
It doesn't happen every time, but it's happened often enough that it's surely worth looking into.
Complaint varies between corruption and "double free or corruption" in successive Coin re-runs:
PASS : tst_QReadWriteLock::multipleReadersBlockRelease() corrupted size vs. prev_size
(repeated a few times) and
PASS : tst_QReadWriteLock::multipleReadersBlockRelease() double free or corruption (!prev)
There is nothing obvious about the test code that would lead to this.
It is, of course, possible QEMU is just being buggy at us.
Attachments
For Gerrit Dashboard: QTBUG-96103 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
370051,2 | Skip tst_QReadWriteLock::multipleReadersLoop on QEMU | dev | qt/qtbase | Status: MERGED | +2 | 0 |
370107,3 | Skip tst_QReadWriteLock::multipleReadersLoop on QEMU | 6.1 | qt/qtbase | Status: MERGED | +2 | 0 |
370108,3 | Skip tst_QReadWriteLock::multipleReadersLoop on QEMU | 6.2 | qt/qtbase | Status: MERGED | +2 | 0 |