@Christian-Ehrlicher yes,i just realize i forget to add sql to QT += core gui sql thanks for respone anyway

Just by loading one page and coming back, we can't make out the memory leak. Try multiple times like this. If you see a increase & no decrease then we can conclude memory leak. If you can send me the complete example, we can try as well.

@SGaist No invalid devices nor problems are reported in the device manager.

IIRC, the two builds are not using the same backend.

@GrecKo I found that it is a bug that is affecting all platforms with certain screen resolutions. Some developers may not notice this issue but the end user may be using a certain screen resolution and be affected by the issue! You can login to https://bugreports.qt.io/ and Vote THIS bug if you also want this bug to be resolved.

@mrjj Ok. I have fixed it temporary by defining in the .pro file: DEFINES += _ATL_NATIVE_INITIALIZATION And also reported it https://bugreports.qt.io/browse/QTBUG-63772 . Thank you.

Nobody has replied, so I've entered it as a bug: https://bugreports.qt.io/browse/QTBUG-63901. I'll see what happens.