Created attachment 42461 [details] Test application to open/close connection Using R7.5 with xserver v1.7.1 and vesa driver 2.3.0, it appears a small leak occurs on each XOpenDisplay/XCloseDisplay call pair. This was encountered during some unrelated testing, and eventually distilled down to those 2 calls. Previously on 6.9.0 this leak did not occur. Our application makes multiple connections over time to the X server, is this wrong or abusive? With the attached trivial test snippet (just XOpenDisplay followed by XCloseDisplay), running it continually increases the memory owned by the X process until it is eventually oom-killed some hours later. I'm working to remedy the limited debugging utilities available on the target machine to get more details. Bug 25029 seems close, but unrelated due to those functions being called on initialization, not per-connection (unless that's not the case of course).
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please file a new report if you continue to experience issues with a current server.
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.