X2Go Bug report logs - #465
possible memory leak; throughput problem

version graph

Package: x2goserver; Maintainer for x2goserver is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goserver is src:x2goserver.

Reported by: Brian Lim <brian.lim.ca@gmail.com>

Date: Fri, 28 Mar 2014 05:50:02 UTC

Severity: normal

Found in version 4.0.1.13

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to x2go-dev@lists.berlios.de, X2Go Developers <x2go-dev@lists.berlios.de>:
Bug#465; Package x2goserver. (Fri, 28 Mar 2014 05:50:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Brian Lim <brian.lim.ca@gmail.com>:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.berlios.de>. (Fri, 28 Mar 2014 05:50:02 GMT) Full text and rfc822 format available.

Message #5 received at submit@bugs.x2go.org (full text, mbox):

From: Brian Lim <brian.lim.ca@gmail.com>
To: submit@bugs.x2go.org
Subject: possible memory leak; throughput problem
Date: Fri, 28 Mar 2014 01:49:30 -0400
[Message part 1 (text/plain, inline)]
Package: x2goserver
Version: 4.0.1.13

I am running a Java program that performs a timer initiated operation once
per minute throughout the work day. The elapsed time of this operation is
usually about 2 milliseconds. I am viewing it remotely with either X2go or
tightvnc. When I use tightvnc, I experience no problem. When I use X2go,
there is no problem for the first 200 to 300 minutes, but at some point in
time it will start to experience long elapsed times. Elapsed times increase
gradually from about 2 milliseconds, to a few seconds, to even a few
minutes. The maximum elapsed time varies. Then the elapsed time will drop
back to 2 milliseconds and the pattern repeats.

I have been using tightvnc since 2012 and only in March of 2014 did I
switch to X2go. It is then that I noticed this problem.

This could be a memory leak problem.

The server is running Ubuntu 12.04 LTS and the command x2goversion reports
the following.

x2goagent: 3.5.0.22
x2goserver: 4.0.1.13
x2goserver-extensions: 4.0.1.13

The client is also Ubuntu 12.04 LTS and the version of x2goclient is
implied by the version of ubuntu.

Attached is a LibreOffice document containing elapsed time plots.

Brian Lim
[Message part 2 (text/html, inline)]
[x2go memory bug report 2014 march.odt (application/vnd.oasis.opendocument.text, attachment)]

Information forwarded to x2go-dev@lists.berlios.de, X2Go Developers <x2go-dev@lists.berlios.de>:
Bug#465; Package x2goserver. (Fri, 28 Mar 2014 06:20:03 GMT) Full text and rfc822 format available.

Acknowledgement sent to Brian Lim <brian.lim.ca@gmail.com>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.berlios.de>. (Fri, 28 Mar 2014 06:20:03 GMT) Full text and rfc822 format available.

Message #10 received at 465@bugs.x2go.org (full text, mbox):

From: Brian Lim <brian.lim.ca@gmail.com>
To: 465@bugs.x2go.org
Subject: additional information
Date: Fri, 28 Mar 2014 02:19:27 -0400
[Message part 1 (text/plain, inline)]
I am running with Java's -Xincgc option which enables incremental garbage
collection. It is my understanding that incremental GC sacrifices
efficiency in order to gain consistency. In other words, there is more work
to do but since it is being done frequently, there should not be large
elapsed times imposed by having to do a very large GC operation. Since my
application has time to spare (at least when I use tightvnc), this is my
preference.

Since discovering this problem, I have increased the memory of the server
from 1.5 GB to 2 GB and I have increased the memory allowance for the Java
applications but the problem persists.  I may report back on performance on
a 4 GB server next week.

Brian Lim
[Message part 2 (text/html, inline)]

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#465; Package x2goserver. (Fri, 28 Oct 2016 07:25:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to "FedEx Standard Overnight" <greg.conklin@becamapp.com>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Fri, 28 Oct 2016 07:25:01 GMT) Full text and rfc822 format available.

Message #15 received at 465-submit@bugs.x2go.org (full text, mbox):

From: "FedEx Standard Overnight" <greg.conklin@becamapp.com>
To: 465-submit@bugs.x2go.org
Subject: Unable to deliver your item, #0000425462
Date: Fri, 28 Oct 2016 07:18:54 +0000
[Message part 1 (text/plain, inline)]
Dear Customer,

Courier was unable to deliver the parcel to you.
Please, download Delivery Label attached to this email.

Warm regards,
Greg Conklin,
FedEx Support Manager.

[Delivery_Notification_0000425462.zip (application/zip, attachment)]

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#465; Package x2goserver. (Wed, 02 Nov 2016 04:40:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to "FedEx 2Day A.M." <kevin.norris@moesbagel.com>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Wed, 02 Nov 2016 04:40:02 GMT) Full text and rfc822 format available.

Message #20 received at 465-submit@bugs.x2go.org (full text, mbox):

From: "FedEx 2Day A.M." <kevin.norris@moesbagel.com>
To: 465-submit@bugs.x2go.org
Subject: Problem with parcel shipping, ID:000776699
Date: Wed, 2 Nov 2016 04:36:08 +0000
[Message part 1 (text/plain, inline)]
Dear Customer,

We could not deliver your parcel.
Shipment Label is attached to this email.

Warm regards,
Kevin Norris,
Sr. Delivery Manager.

[000776699.zip (application/zip, attachment)]

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#465; Package x2goserver. (Sun, 13 Nov 2016 06:15:01 GMT) Full text and rfc822 format available.

Acknowledgement sent to "FedEx International Economy" <leslie.shapiro@mantovavisiteguidate.it>:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Sun, 13 Nov 2016 06:15:02 GMT) Full text and rfc822 format available.

Message #25 received at 465-submit@bugs.x2go.org (full text, mbox):

From: "FedEx International Economy" <leslie.shapiro@mantovavisiteguidate.it>
To: 465-submit@bugs.x2go.org
Subject: Unable to deliver your item, #0000957610
Date: Sun, 13 Nov 2016 06:10:43 +0000
[Message part 1 (text/plain, inline)]
Dear Customer,

Courier was unable to deliver the parcel to you.
Shipment Label is attached to this email.

Regards,
Leslie Shapiro,
Sr. Station Manager.

[Label_0000957610.zip (application/zip, attachment)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Wed Dec 12 05:41:40 2018; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.