-
Bug
-
Resolution: Done
-
P2: Important
-
None
-
5.9.0, 5.9.1
-
None
-
Qt 5.9.1-0-20170629 prebuilt binaries for Linux 64bits (also tested on 5.9.0)
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile
OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.1.3
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
Linux 4.11.8-1-default #1 SMP PREEMPT Thu Jun 29 14:37:33 UTC 2017 (42bd7a0) x86_64 x86_64 x86_64 GNU/LinuxQt 5.9.1-0-20170629 prebuilt binaries for Linux 64bits (also tested on 5.9.0) OpenGL vendor string: Intel Open Source Technology Center OpenGL renderer string: Mesa DRI Intel(R) Sandybridge Mobile OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.1.3 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile Linux 4.11.8-1-default #1 SMP PREEMPT Thu Jun 29 14:37:33 UTC 2017 (42bd7a0) x86_64 x86_64 x86_64 GNU/Linux
-
102fef33f14f21869725ebfa46d57c31ec4002b3
Summary
The memory allocated by SceneLoader isn't released when the Scene3D it belongs to is destroyed.
What did you do?
I use a Loader to load a QML Scene3D. This scene only comprises an Entity that is filled by a SceneLoader component, which reads an OBJ file.
What did you expect to happen?
I expect the memory allocated by the SceneLoader to be freed.
What happened instead?
The (huge amount) of memory allocated isn't freed. This can lead to gigabytes of memory lost after a few minutes, which makes the SceneLoader component unusable.
Attached project
The attached simple project loads and unloads a Scene3D that have a SceneLoader every 5 seconds, so you can see the the memory consumption growing indefinitely.
According to the Valgrind dump it seems that it's the memory allocated by the Assimp plugin that is not freed.
- is replaced by
-
-
- Open
-