Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
5.1.0 , 5.1.1, 5.2.0, 5.2.1, 5.3.1, 5.3.2, 5.4.0, 5.4.1, 5.4.2, 5.5.0
-
None
-
Windows 7 x64, Windows 8.1 x64
-
3799188e704e48ff8e9aa728cd76101b15f21fd2, b27a01a86e614207025e569926d0c419857e8965
Description
This is very easy reproducible issue. All you need to do is just create a blank QML project based on the ApplicationWindow component and that's it. Now, if you run the project and start clicking on the menu, you will see that every time after menu was opened, it leaks about ~6 MB of memory, so if you click fast, in one minute it will be about 600 megabytes. After approximately 650 MB, the application stops render the menu (you can see it on the attached screenshot) and throws this to output:
QOpenGLShaderProgram: could not create shader program
QOpenGLShader: could not create shader
QOpenGLShader: could not create shader
shader compilation failed:
""
QOpenGLShaderProgram::uniformLocation( qt_Matrix ): shader program is not linked
QOpenGLShaderProgram::uniformLocation( opacity ): shader program is not linked
After 750 megabytes it will occur to crash.
I found it when I was working on my QML Particle Editor tool, so you could use it for tests too. This definitely not a qmlscene bug, since it doesn't matter if you run the project using qmlscene or if you compile it. Here's the link: https://github.com/wearyinside/qmlparticleeditor