- 
    
Epic
 - 
    Resolution: Fixed
 - 
    
P1: Critical
 - 
    6.6
 - 
    None
 
- 
        qmlincrementalgc
 - 
        7461ae2a9 (dev), b9d37a328 (dev), 14f549fdc (dev), bdb624659 (dev)
 
Rough outline of required steps:
- Prepare tests for introduction of incremental gc ✔
 - Introduce incremental mark phase ✔
 - Introduce incremental sweep phase ✔
 - Make feature (build-time) configurable †
 - Validate performance (of the engine), optimize if necessary
 - Investigate if we need to change when to invoke the gc if its in incremental mode ✔
 - Document knobs which we might expose
 
† It's no longer possible to make the whole feature optional – we moved away from black allocations while the gc is running, so now the write barrier is vital even in non-incremental mode. It might still make sense to expose knobs to disable incremenatl gc.
- relates to
 - 
                    
QTBUG-123426 Assert in qml engine "Q_ASSERT(m()->internalClass->vtable)"
-         
 - Closed
 
 -         
 - 
                    
QTBUG-129241 Crash at QV4::Value::as<T>
-         
 - Closed
 
 -         
 
- resulted from
 - 
                    
QTBUG-117634 QML Garbage Collection takes excessive time
-         
 - Closed
 
 -         
 
- mentioned in
 - 
                    
Page Loading...