[Mesa-users] Mesa XWindows memory leak causing application instability

[Rick Irons]

Hi Chuck,

Thanks for the suggestion.  I am actually planning on working on building and experimenting with Mesa on both LINUX and Windows in the coming weeks.  I will try out the configuration that you recommended.

Thanks,
Rick

From: Chuck Atkins [mailto:chuck.atkins at kitware.com]
Sent: Monday, June 19, 2017 11:32 AM
To: Rick Irons <Rick.Irons at mathworks.com>
Cc: Brian Paul <brianp at vmware.com>; mesa-users at lists.freedesktop.org
Subject: Re: [Mesa-users] Mesa XWindows memory leak causing application instability

Hi Rick,
One of my colleagues tried the configuration that you recommended and was unable to reproduce the issue.  On further investigation he determined that the Gallium configuration doesn’t call XShmDetach.  He added a call to XShmDetach and was then able to recreate the issue.  Is it intentional (and appropriate) that the XShmDetach call is absent from the Gallium configuration?

Unfortunately, I can't speak much to the implementation side.  However, we make extensive use of a bare-minimum software-only implementation of mesa as a backup renderer using the suggested configuration and have not seen issues with it so my hope was that it could give you a usable library while waiting for the issue to be addressed in classic-xlib (if at all).  It may be worh using this configuration anyways since it's built on the gallium infrastructure which is much more likely to see regular and active maintenence than the classic-xlib implementation.

As for debugging the details of the bug, I'll have to defer to Brian for that.
- Chuck

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/mesa-users/attachments/20170619/b9d18f60/attachment.html>