On Fri, Jan 17, 2020 at 11:56 AM Johannes Töger <johannes.to...@med.lu.se> wrote: > We are using x2go for a common compute server at our department. We have > users both on the local LAN and connections to the other side of Europe that > work really well. Being able to close the client and have computations still > running in a GUI environment is great. > > However, I think we have encountered a bug. Some (but not all) of the > long-running x2goagent processes start taking a lot of memory, ~30 GB. This > adds up quickly so that the other users can’t do their work. Below you can > see how user3 and user7 have x2goagent processes with large memory use (RSS > column). > > How can I go about debugging this? I have quite a bit of Linux experience, > but I don’t know where to start on this one since I don’t know much about how > x2go works internally. > > Server is on Ubuntu Server 18.04.1 LTS, (x2goserver > 4.1.0.3-0~1708~ubuntu18.04.1). Clients are on Windows 10, version. 4.1.2.0. > > johannes@compute-server:~$ ps -o pid,lstart,rss,user $(pgrep x2goagent)
What version of x2goagent resp. nxagent are you using? dpkg -l nx-libs? Can you please run xrestop within such a session and check if there are numbers that are far away from those of a fresh session? You probably cannot answer that due to your usage scenario, but anyway: does this also happen when you do not disconnect/reconnect? What are you running inside the session? You could run x2goagent with valgrind to identify memory leaks but I am unsure if that is working on a stock installation ( I don't do the packaging for Debian/Ubuntu so I don't know if the deliveres binaries allow for decent analysis/output). I'll check that this weekend. Uli _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
