I have Xvnc running via xinetd to supply multiple vnc sessions on a server. After the upgrade I nearly see 100% CPU per Xvnc process, which is deadly when running up to 10 Xvnc sessions. Before the upgrade this was no issue. xinetd justs starts the Xvnc process, then lightdm kicks in via xdmcp, and even the quite static login page brings the Xvnc process to nearly 100% CPU.
Can you give me the parameters to Xvnc? Or the file in xinetd.d you use to start it?
-inetd -query localhost -once -geometry 1280x1024 -depth 16 -pn -fp somefontpaths IdleTimeout=3600 securitytypes=none are my parameters. AS I said, this used to work like a charm before the update
Created attachment 902205 [details] xinetd configuration file this is my xinetd configuration file for opening a xdmcp login session via VNC
strange, running this on my amd64 machine I don't have any problems, running it under x86 I immediately see Xvnc among to the top processes.
I tried to replicate your configuration and it works fine for me (on amd64 also). I don't have an x86 to test it, but I suppose it's something specific to your case. Check if you have enough memory, maybe try a strace, and if you cannot figure it out I suggest opening an issue with upstream, maybe they can help. https://github.com/TigerVNC/tigervnc/issues Also please post an `emerge --info`, maybe there is something there (I didn't know this was on 32 bit, for example).
Created attachment 902242 [details] emerge --info here's my emerge info. I know the profile is not supported anymore, did not find time to do the update, also glibc is outdated, need to doublechech compatibility with 3rd party closed source application (SCADA)
I don't see anything obvious, maybe try to compile it again without ccache (or with CCACHE_RECACHE=yes), I don't have other ideas.
(In reply to Viorel Munteanu from comment #7) > I don't see anything obvious, maybe try to compile it again without ccache > (or with CCACHE_RECACHE=yes), I don't have other ideas. OK, maybe I'll try this, but as I tested Xvnc on a amd64 machine already, I will move the Xvnc to this host and do the xdmcp query to the original host, instead of running both xdmcp and Xvnc server on the same host. So I can achieve some memory/cpu offload from the 32 bit VM
