Xorg VRAM leak because of Qt/OpenGL Application

mwestphal

Well, the minimum example require sadly to build the whole application. I was not able to reproduce it using only our QOpenGLWindow reimplementation. That is why I'm not sure that it is a bug in Qt our in our Application.

aha_1980

@mwestphal if you have a commercial licence, then the support can help you with priblems in your code also.

if you use open source Qt, then you have to provide a minimal example for bug reports, i.e. track down the actual problem (which is always good!)

mwestphal

Since the whole application is OpenSource and Free, I do not have any problem with sharing it, it is simply that I am afraid that a example with this so many lines will not be considered and quite hard to pin down for somebody not knowing the code.

I was more hoping for advices on how this could happen as it would help me track it down.

sierdzio

@mwestphal said in Xorg VRAM leak because of Qt/OpenGL Application:

I was more hoping for advices on how this could happen as it would help me track it down.

I have zero experience with QOpenGLWidget and containerWidget, unfortunately.

One recommendation that springs to mind when leaks are a problem: run your app through valgrind and / or clang's address sanitizer. They are often quite good at finding such issues.

mwestphal

@sierdzio : That we did, and actually corrected a few memory leaks in the process. But not related to this issue.
Since this is Xorg leaking on the VRAM, it would have been quite a wild luck to fix it this way anyway.

wrosecrans

Have you tried building your application with Address Sanitizer to see if it helps you identify the source of the leak? It is very helpful with that sort of problem.

aha_1980

@wrosecrans have you read the last two responses? ;)

wrosecrans

@aha_1980

D'oh. Maybe this plan to give up drinking so much coffee in the mornings wasn't such a great idea. :)

I guess I just think using Address Sanitizer is advice that is worth repeating! One thing I will add is that it's not clang specific -- recent versions of gcc will accept the same command line parameters to use it.

mwestphal

The issue was resolved thanks to an intense debugging session.

The leak was caused by NULL parenting the parent of the windowContainer containing the QVTKOpenGLWindow just before deletion.

This code was here before when we used a QOpenGLWidget and it caused no issue. In any case, NULL parenting a widget before deletion is useless so removing the line resolve the issue.

This leak shouldn't happen though, even in this situation, so I have opened a Qt issue to report it.

sierdzio

Great, thanks for investigating and reporting the bug!