Thanks to you both for getting involved in this. I've been swamped with other things, so not much to report. I did manage to plot the x2goagent memory use over time though. Maybe this can help.
Link to plot: https://imgur.com/a/lDqZ2zd As you see, several users have a constant memory use. However, 3 of them have a constantly increasing memory use. So not isolated incidents that leak, but rather a continuous drip. — Johannes Töger Associate Senior Lecturer Cardiac MR Group Department of Clinical Sciences Lund, Clinical Physiology Lund University, Sweden -----Original Message----- From: x2go-user <x2go-user-boun...@lists.x2go.org> On Behalf Of Bernd Schubert Sent: Thursday, January 23, 2020 16:11 To: Ulrich Sibiller <ul...@gmx.de> Cc: x2go-user@lists.x2go.org Subject: Re: [X2Go-User] Long-running x2goagent, high memory usage On 1/23/20 3:41 PM, Ulrich Sibiller wrote: > Ok, that's fine, too! I am curious about the results! > > Uli > > PS: Well, Johannes started the thread and I tried to help him, I am a > bit confused that now you (Bernd) kick in. Are you a colleague of > Johannes or are you also seeing that problem? Ah sorry, no, I'm just reading the thread. I had similar issues in the past with x2go, but right now long running sessions work pretty well. I'm also coding all the time and the compiler sanitizers are great help and work so much faster than valgrind - I just tried to point that out. Sorry for confusion. - Bernd _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
