-
Bug
-
Resolution: Fixed
-
P1: Critical
-
5.15.8
-
None
-
Windows:
QSSG.trace_info: GLSL version: 4.30 - Build 26.20.100.7812
QSSG.trace_info: GL version: 4.3.0 - Build 26.20.100.7812
QSSG.trace_info: HW vendor: Intel
QSSG.trace_info: Vendor renderer: Intel(R) UHD Graphics 620
Integrity:
opengl texture atlas dimensions: 2048x1024
R/G/B/A Buffers: 8 8 8 8
Depth Buffer: 24
Stencil Buffer: 8
Samples: 0
GL_VENDOR: Qualcomm
Adreno (TM) 640
OpenGL ES 3.2
Windows: QSSG.trace_info: GLSL version: 4.30 - Build 26.20.100.7812 QSSG.trace_info: GL version: 4.3.0 - Build 26.20.100.7812 QSSG.trace_info: HW vendor: Intel QSSG.trace_info: Vendor renderer: Intel(R) UHD Graphics 620 Integrity: opengl texture atlas dimensions: 2048x1024 R/G/B/A Buffers: 8 8 8 8 Depth Buffer: 24 Stencil Buffer: 8 Samples: 0 GL_VENDOR: Qualcomm Adreno (TM) 640 OpenGL ES 3.2
-
Integrity,
Windows
-
3d93b4c180 (qt/tqtc-qtquick3d/5.15.10) badb1d8319 (qt/tqtc-qtquick3d/5.15.10) badb1d8319 (qt/tqtc-qtquick3d/5.15-opensource)
Hello!
I've detected a memory leak in our application when we load with Loader an Item that contains a Texture (Quick3D) with an image source. This issue appeared in both debug and release, with images of formats PNG and ASTC.
The attachment contains a small test application that loads/unloads View3D when the button is clicked. This view contains a simple rectangle model that uses a material and a texture with an image as a source. Each time Loader loads the view the allocated memory is increased by few Mb and is never being released until the application is closed (according to task manager and QML profiler).
- relates to
-
-
- Closed
-