cause this behavior ?
Could this be a Xorg bug ?
If not, what could, in our code create this behavior ?
Best regards,
Mathieu Westphal
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Info: https://lists.x.o
r and over, the VRAM will get completelly
full and Xorg starts leaking in RAM
Once the RAM is full, OpenGL starts to fails completelly.
I did not test Wayland.
Do you know what could cause this behavior ?
Could this be a Xorg bug ?
If not, what could, in our code create this behavior ?
Best regards
Hi Dennis, Aaron,
Firstly, Dennis, you may have missed that it is *Xorg *leaking in the *VRAM
*and not releasing it even* after my application is exited*/killed
completely.
I have been monitoring the RAM as well, it is fine and my application is
not leaking but somehow forces Xorg to allocate grap
UG-69429> to report it.
Sorry for the noise, as Xorg is probably not to blame.
Mathieu Westphal
On Tue, Jul 3, 2018 at 8:14 AM, Mathieu Westphal <
mathieu.westp...@kitware.com> wrote:
> Hi Dennis, Aaron,
>
> Firstly, Dennis, you may have missed that it is *Xorg *leaki
.
My question would be : How to programmatic ally ensure that my Qt
application does not mistakenly try to use the extra composite visual.
Thanks,
Mathieu Westphal
___
xorg@lists.x.org: X.Org support
Archives: http://lists.freedesktop.org/archives/xorg
Thanks for your help, we indeed add a call to
fmt.setAlphaBufferSize(1);
Mathieu Westphal
On Fri, Sep 21, 2018 at 8:11 PM Alan Coopersmith <
alan.coopersm...@oracle.com> wrote:
> On 09/21/18 10:54 AM, Adam Jackson wrote:
> >> Since Composite is not enabled by default, it is