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

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#465: additional information
Reply-To: Brian Lim <brian.lim.ca@gmail.com>, 465@bugs.x2go.org
Resent-From: Brian Lim <brian.lim.ca@gmail.com>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: owner@bugs.x2go.org
Resent-Date: Fri, 28 Mar 2014 06:20:03 +0000
Resent-Message-ID: <handler.465.B465.139598756927681@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: followup 465
X-X2Go-PR-Package: x2goserver
X-X2Go-PR-Keywords: 
Received: via spool by 465-submit@bugs.x2go.org id=B465.139598756927681
          (code B ref 465); Fri, 28 Mar 2014 06:20:03 +0000
Received: (at 465) by bugs.x2go.org; 28 Mar 2014 06:19:29 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on
	ymir.das-netzwerkteam.de
X-Spam-Level: 
X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM,
	HTML_MESSAGE,T_DKIM_INVALID autolearn=ham version=3.3.2
Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179])
	by ymir (Postfix) with ESMTPS id 57D1F5DB1B
	for <465@bugs.x2go.org>; Fri, 28 Mar 2014 07:19:28 +0100 (CET)
Received: by mail-vc0-f179.google.com with SMTP id ij19so5563962vcb.10
        for <465@bugs.x2go.org>; Thu, 27 Mar 2014 23:19:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=uv4mDN4SSJPArBVGuBU8NPwRhIqsBiGIJofSMHH8aUE=;
        b=iMhW+uvUGYVuLnqBHMVQGPcmAuDduj8rlQxldo7Lg0ct8y6/xzXdbuLFLKJfIEOqJQ
         xEwTv83OdxSkvZIBWKoQpo52VAb7qSnrUThRfVuEtmcqs7LnCOc5t4xZEBVImT0E1Fc3
         TkAnpw8sVUKiVHRBDGUxiidG1fhBHGDgN1pHJs/NRLaRsdHu/1dYj6nCeILhfaUT7xop
         Hy+I9hm0kyQSLXCp/adYGxS1mccXicXlHl03TxVfBp/g8hegKiD6wktsXEr6ZQSTJTWd
         Ugc9NPkcKntt3/2n0MbRksT/AVDSo5cjeq5Utc/r6evH24JgwV8KBeqWXkkCg7cJy7Sn
         s6vQ==
MIME-Version: 1.0
X-Received: by 10.221.29.137 with SMTP id ry9mr5546295vcb.6.1395987567243;
 Thu, 27 Mar 2014 23:19:27 -0700 (PDT)
Received: by 10.58.202.133 with HTTP; Thu, 27 Mar 2014 23:19:27 -0700 (PDT)
Date: Fri, 28 Mar 2014 02:19:27 -0400
Message-ID: <CA+GY1+C0DtDwtGN-JyHZW108zByTUxvCh==oM5os2rAeAN+Vqw@mail.gmail.com>
From: Brian Lim <brian.lim.ca@gmail.com>
To: 465@bugs.x2go.org
Content-Type: multipart/alternative; boundary=001a1133935c0e78ec04f5a4af29
[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)]

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Jun 20 18:41:50 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.