On Wed, 2010-05-19 at 11:46 -0400, John A. Sullivan III wrote:

Hello, all. We are seeing this with enough regularity that it is alarming. Our first client uses Konqueror heavily in their work process. They usually open files from it rather than from within the applications, they email directly from it, etc. The environment is Lenny + Backports with a few updates from Squeeze. We are using KDE 3.5. X2Go is 3.0.1-4 on the client (all windows stations) and 3.0.1-5 for server.

We have not been able to track down the trigger but the user's Konqueror will freeze partly painted. x2goagent consumes all the CPU and Konqueror's memory usage grows to frightening amounts (e.g., 18GB). How can we track down and kill this serious bug? Thanks - John Hello, all. We continue to see this serious situation. Today, it manifested itself very strangely. We could see Konqueror consuming almost 3G of RAM and x2goagent consuming 100% of the CPU. Oddly, when I went to connect to the X2GoServer as that user, it let me in and Konqueror did not appear to be running. I terminated the session and ran top from a console on the same system and it still showed a fully running KDE session for that user yet I was not prompted to resume a running session when connecting.

I took backtraces of Konqueror and X2GoAgent but, since this was a production, client system with no debugging installed, there is not much to show. I will attach the files anyway. I did attach an strace to x2goagent which I will also attach. It indeed shows rather repetitive behavior! Any idea what is going on? This is quite serious. Thanks - John