Details
-
Bug
-
Resolution: Invalid
-
P1: Critical
-
None
-
6.4.1, 6.4.2, 6.5.0
-
None
-
Static build of Qt 6.4.1/6.4.2/6.5.0
MacOS Ventura 13.1 / Xcode 14.2 / Windows 10
perl init-repository --module-subset=qt5compat,qtbase,qtdeclarative,qtimageformats,qtmultimedia,qtshadertools,qtsvg,qtwebsockets
./configure -static -debug-and-release -nomake examples -nomake tests -nomake benchmarks -nomake manual-tests -nomake minimal-static-tests
Static build of Qt 6.4.1/6.4.2/6.5.0 MacOS Ventura 13.1 / Xcode 14.2 / Windows 10 perl init-repository --module-subset=qt5compat,qtbase,qtdeclarative,qtimageformats,qtmultimedia,qtshadertools,qtsvg,qtwebsockets ./configure -static -debug-and-release -nomake examples -nomake tests -nomake benchmarks -nomake manual-tests -nomake minimal-static-tests
-
macOS,
Windows
Description
When using such components as ScrollBar on a ListView or a Button, the application crashes if there are consecutive deletion and instantiation of QQuickView / QQApplication
In order to reproduce this crash with the example provided in attachment, you will need to have a static build of Qt. The crash does not happen when using a non static build of Qt
I have also found that the type of import of QtQuick.Controls also influences the outcome. If I'm specific about the type of import, eg: QtQuick.Controls.Basic, the crash also does not happen.