summaryrefslogtreecommitdiffstats
path: root/src/testlib/qtesthelpers_p.h
diff options
context:
space:
mode:
authorLaszlo Agocs <laszlo.agocs@qt.io>2021-07-27 19:42:27 +0200
committerLaszlo Agocs <laszlo.agocs@qt.io>2021-08-02 14:35:33 +0200
commitb594374ba84da986c5ebc93984961040338465d0 (patch)
tree41880eaf968ce0c5be934612a71edc61b0dbab58 /src/testlib/qtesthelpers_p.h
parentee68257b61268ef8f5f4c9b4090d8a1624cd98ce (diff)
rhi: Be more graceful when one destroys a resource after the QRhiHEADdev
One is a bad application or library in this case, but nonetheless we should handle this more gracefully then just crashing due to the QRhi already having been destroyed. Mainly because in Qt 5 one could get away with the same: releasing OpenGL objects underneath, for example, a QSGPlainTexture with no (or wrong) GL context did not generate any user visible fatal errors. So we should not crash in Qt 6 either with these code bases. In debug builds or when QT_RHI_LEAK_CHECK is set, one will get the unreleased resources warning printed in Qt 6, which is a step forward compared to Qt 5. So there is still some indication that something is badly designed, even if the application survives. Task-number: QTBUG-95394 Pick-to: 6.2 Change-Id: I944f4f425ff126e7363a82aff926b280ccf1dfc3 Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org> Reviewed-by: Andy Nichols <andy.nichols@qt.io>
Diffstat (limited to 'src/testlib/qtesthelpers_p.h')
0 files changed, 0 insertions, 0 deletions