Date: Sat, 26 Jun 2004 01:18:42 -0400 From: Parv <parv@pair.com> To: Pav Lucistnik <pav@FreeBSD.org> Cc: klikes@doit.in.gov Subject: Re: ports/68341: xsysinfo memory leak Message-ID: <20040626051842.GA72944@moo.holy.cow> In-Reply-To: <200406252124.i5PLOApd021882@freefall.freebsd.org> References: <200406252124.i5PLOApd021882@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <200406252124.i5PLOApd021882@freefall.freebsd.org>, wrote Pav Lucistnik thusly... > > Synopsis: xsysinfo memory leak > > State-Changed-From-To: open->feedback > State-Changed-By: pav > State-Changed-When: Fri Jun 25 21:23:28 GMT 2004 > State-Changed-Why: > Do you have any patches to fix it? I'm afraid we don't > have manpower to fix general software problems in third-party > software. We're only packaging it. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=68341 The PR does not specify the running time to see bloom in memory usage. Keeping that in mind following is what i got so far on FreeBSD 4.9-p9 while there was not much activity ... PID NI RSZ VSZ %MEM %CPU STARTED STAT TIME COMMAND 312 5 1684 2896 0.4 0.5 9:04AM SN 2:38.12 xsysinfo 312 5 1668 2896 0.4 0.0 9:04AM SN 2:58.26 xsysinfo 312 5 1652 2896 0.4 0.0 9:04AM SN 3:13.40 xsysinfo 312 5 1636 2896 0.4 0.2 9:04AM SN 3:20.35 xsysinfo 312 5 1636 2896 0.4 0.6 9:04AM SN 3:21.21 xsysinfo 312 5 1604 2896 0.4 0.4 9:04AM SN 3:25.95 xsysinfo 312 5 1604 2896 0.4 0.0 9:04AM SN 3:25.95 xsysinfo 312 5 1504 2896 0.4 0.0 9:04AM SN 3:41.79 xsysinfo ...and the command was stared via xinitrc thusly... xsysinfo -geometry 190x80+90-20 -interval 3 -nonfs - Parv --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040626051842.GA72944>