MobileRead Forums - View Single Post

KevinH · 10-01-2024, 02:51 PM

This is exactly what happened with the macOS memory leak Qt fixed earlier (but the fix was only for Apple Metal graphics). There was even a qml example program that opened a QtWebEngine WebEngineView and just constantly resized it, and you could watch the memory use just grow.

I will see if I can find the qml sample program and Qt bug.

Update: See https://bugreports.qt.io/browse/QTBUG-124353

In that issue is a bug.qml test case that you can run with the command:

qml bug.qml

and just watch the memory consumption grow due to huge memory leak. On arm64 mac the gpu and main memory s shared and you can see the gpu memory just grow.

It was fixed for MacOS in qt 6.7 with a patch.

Perhaps something similar is happening on Windows or Linux.

10-01-2024, 02:51 PM	#7
KevinH Sigil Developer Posts: 8,437 Karma: 5702578 Join Date: Nov 2009 Device: many	This is exactly what happened with the macOS memory leak Qt fixed earlier (but the fix was only for Apple Metal graphics). There was even a qml example program that opened a QtWebEngine WebEngineView and just constantly resized it, and you could watch the memory use just grow. I will see if I can find the qml sample program and Qt bug. Update: See https://bugreports.qt.io/browse/QTBUG-124353 In that issue is a bug.qml test case that you can run with the command: qml bug.qml and just watch the memory consumption grow due to huge memory leak. On arm64 mac the gpu and main memory s shared and you can see the gpu memory just grow. It was fixed for MacOS in qt 6.7 with a patch. Perhaps something similar is happening on Windows or Linux. Last edited by KevinH; 10-01-2024 at 03:04 PM.