ports/68341: xsysinfo memory leak

Kevin T. Likes klikes at doit.in.gov
Mon Jun 28 14:58:13 UTC 2004


I haven't had a chance to watch things closely.  I do know the copy I started 
Friday was at 112M today, but when I restarted it was 3352K  2304K (Sise, RSS).
The options on it were: -geometry 188x112-0+435.  Here's some ps output (with 
timestamps).  Seems to be growing quickly.  If you're not seeing this on 4.9, 
it may be something with 5.2.1.

[sfra15 at jaka /usr/ports/www]$ while : ; do date; ps -lp 30898; sleep 5; done
Mon Jun 28 09:53:05 EST 2004
  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
  105 30898   821   1 101  5  3540 2492 select SN    p1    0:02.25 xsysinfo 
-geometry 188x112-0+435
Mon Jun 28 09:53:10 EST 2004
  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
  105 30898   821   0 101  5  3544 2496 select SN    p1    0:02.27 xsysinfo 
-geometry 188x112-0+435
Mon Jun 28 09:53:15 EST 2004
  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
  105 30898   821   1 101  5  3544 2496 select SN    p1    0:02.30 xsysinfo 
-geometry 188x112-0+435
Mon Jun 28 09:53:20 EST 2004
  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
  105 30898   821   0 101  5  3548 2500 -      RN    p1    0:02.31 xsysinfo 
-geometry 188x112-0+435
Mon Jun 28 09:53:25 EST 2004
  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
  105 30898   821   0 101  5  3552 2504 select SN    p1    0:02.34 xsysinfo 
-geometry 188x112-0+435
Mon Jun 28 09:53:30 EST 2004
  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
  105 30898   821   0 101  5  3552 2504 select SN    p1    0:02.36 xsysinfo 
-geometry 188x112-0+435
Mon Jun 28 09:53:35 EST 2004
  UID   PID  PPID CPU PRI NI   VSZ  RSS MWCHAN STAT  TT       TIME COMMAND
  105 30898   821   1 101  5  3556 2508 select SN    p1    0:02.38 xsysinfo 
-geometry 188x112-0+435

So every 5-10 seconds it grows by 4K.  There is hardly any system load.

--ktl

p.s. per other e-mails, I've cc:ed the maintainer on this.

In message <20040626051842.GA72944 at moo.holy.cow>, Parv writes:
>in message <200406252124.i5PLOApd021882 at 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
>
>-- 
>




More information about the freebsd-ports-bugs mailing list