Thanks for the quick response Adam. I've seen this behavior across multiple graphics applications and graphics drivers. This is an extreme use case I'm trying out. So, there's a possibility of this use case not being handled correctly by any of the applications or graphics drivers. But I also see some basic X functionality, like closing the window using the "x" button, not working properly with windows opened past the 256 limit. This happens with a modified limit of 512. I had to use xkill to close those windows. Any thoughts about this?
Thanks Anuj On Fri, May 5, 2023 at 2:55 PM Adam Jackson <a...@redhat.com> wrote: > No, just MAXCLIENTS. Probably vkcube (or the driver it's using) should > fail more robustly when it can't connect to the display, instead of letting > you render without presenting though. > > On Fri, May 5, 2023 at 5:28 PM Anuj Phogat <anuj.pho...@gmail.com> wrote: > >> Hi All, >> >> I've been trying to run the maximum number of instances of vkcube (Vulkan >> application) >> in Ubuntu 22.04. I'm hitting one of these X errors when I get past ~256 >> instances: >> - "Maximum number of clients reached" >> - "_XSERVTransSocketUNIXAccept: accept() failed" >> >> I was able to get past these errors by adding below code in xorg conf >> file passed to Xorg >> using '-config' option: >> Section "ServerFlags" >> Option "MaxClients" "512" >> EndSection >> >> Now I'm not seeing X errors about the limit but X windows past the 256 >> limit don't render >> anything. Do I need to adjust any other limits (other than MAXCLIENTS) to >> make instances >> past 256 limit render as expected ? I would appreciate any pointers to >> help me debug and >> resolve this issue. >> >> Adding Adam and Olivier in Cc as I noticed a few old patches from them >> around changing >> MAXCLIENTS. >> >> Thanks >> Anuj >> >
