Details
-
Bug
-
Resolution: Done
-
P2: Important
-
5.6.1, 5.7.1, 5.8.0, 5.12
-
Windows 10, ArchLinux (gcc, clang)
-
-
69d76d59cec0dcff4c52eef24e779fbef14beeca (qt/qtdeclarative/5.12) d8110b53ed9ee4d69b92e602e812c6311c1b863b
Description
Whenever a new Geometry object (with its name) is added, a dynamic property is added to the used JSObject and when Geometry object is removed, the corresponding dynamic property is also removed.
when dealing with thousands of objects, the memory consumption is huge (magnitude of GBs)
Attached example reproduces it:
when this little example starts it takes around 600mb of memory and when it destroy (mouse click on window) memory consumption keeps going up and up until it runs out of the memory.
Using it as simple array keeps the memory consumption around 50mb only.
Attachments
Issue Links
- resulted in
-
QTBUG-91687 QML fails to run benchmarks in qmlbench's v8bench directory
- Closed
For Gerrit Dashboard: QTBUG-58559 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
256324,2 | V4: Don't mark InternalClass::parent when garbage collecting | 5.12 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
256503,5 | Trigger the garbage collector when allocating InternalClass objects | 5.12 | qt/qtdeclarative | Status: MERGED | -2 | 0 |
423541,11 | V4: Mark InternalClass parents when running GC | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
424906,2 | V4: Mark InternalClass parents when running GC | 6.4 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
424907,2 | V4: Mark InternalClass parents when running GC | 6.3 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
424915,2 | V4: Mark InternalClass parents when running GC | tqtc/lts-6.2 | qt/tqtc-qtdeclarative | Status: MERGED | +2 | 0 |
424916,6 | V4: Mark InternalClass parents when running GC | tqtc/lts-5.15 | qt/tqtc-qtdeclarative | Status: MERGED | +2 | 0 |