Details
-
Task
-
Resolution: Fixed
-
P1: Critical
-
6.8
-
None
-
970828df9 (dev), bb3999a22 (dev), d6d224892 (dev), e19750538 (dev), b0d753ee3 (dev), bdb624659 (dev), 241b8693d (dev)
Description
It seems that the main use case for black allocations was preventing objects from getting swept by the gc https://codereview.qt-project.org/c/qt/qtdeclarative/+/320532 . But this was only possible because the gc lacked an active write barrier.
Now that we do have a write barrier, we should revisit this (as it introduces gotchas in a few places).
Attachments
Issue Links
- relates to
-
QTBUG-123426 Assert in qml engine "Q_ASSERT(m()->internalClass->vtable)"
-
- Closed
-
-
QTBUG-129241 Crash at QV4::Value::as<T>
-
- Closed
-