Bug 109958 - Xorg memory leak when using llvmpipe/softpipe
Summary: Xorg memory leak when using llvmpipe/softpipe
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Gallium/vmwgfx (show other bugs)
Version: 18.3
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-11 11:11 UTC by joney
Modified: 2019-09-18 20:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description joney 2019-03-11 11:11:29 UTC
Hello,

there seems to be a major memory leak in Xorg in combination with the VMware driver and the llvmpipe/softpipe renderer. It can be easily reproduced using glxgears. This works even on some real hardware systems when forcing software rendering (depending on the graphics driver which is used):

export GALLIUM_DRIVER="llvmpipe"
export LIBGL_ALWAYS_SOFTWARE="true"
glxgears -info

When glxgears is using llvmpipe or softpipe as renderer, it should be reproducible. Grab a corner of the glxgears window and quickly move it around (i.e., resize the window continuously) while watching Xorg memory which rapidly starts to grow. When stopping the resizing, memory usage stays constant and drops again after closing the window.

On my systems running in VirtualBox and vSphere, llvmpipe was used by default, so the exports are not necessary and the problem always occurs. In VirtualBox, the problem did not occur when I enabled 3D acceleration (VM settings -> Display -> Screen) as then SVGA3D is used as renderer.

I could observe this behavior on Ubuntu 18.04 (with stock Mesa 18.2.2 and also using the Ubuntu-X team PPA with Mesa 18.3.3), Ubuntu 18.10, Fedora 29 (Xwayland) and Debian 9, so I suspect it might be something in Mesa. I could not find an existing bug report that seems to match this problem so I opened this one.
Comment 1 joney 2019-03-11 12:48:42 UTC
After searching a little bit more I just found https://bugs.freedesktop.org/show_bug.cgi?id=109641 which looks like it might be the same issue.
Comment 2 GitLab Migration User 2019-09-18 20:14:39 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/890.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.