Your message dated Sun, 17 Jan 2010 16:25:20 +0100
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #201395,
regarding licq memory hogitude
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
201395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=201395
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: licq
Version: 1.2.6-2
the licq process uses absurd amounts of memory.
thats the /proc/$LICQ_PID/status:
Name: licq
State: S (sleeping)
Tgid: 2354
Pid: 2354
PPid: 2353
TracerPid: 0
Uid: 1000 1000 1000 1000
Gid: 29 29 29 29
FDSize: 32
Groups: 29
VmSize: 90304 kB
^^^^^^^^
VmLck: 0 kB
VmRSS: 11448 kB
VmData: 8556 kB
VmStk: 36 kB
VmExe: 560 kB
VmLib: 14680 kB
SigPnd: 0000000000000000
SigBlk: fffffffefffbfeef
SigIgn: 8000000000000000
SigCgt: 0000000380010400
CapInh: 0000000000000000
CapPrm: 0000000000000000
CapEff: 0000000000000000
And yes, it actually _feels_ that it`s huge :-)
regards, Samium Gromoff
--- End Message ---
--- Begin Message ---
Closing old bug that should be fixed in version 1.3.0 according to upstream.
Please reopen if the problem can be reproduced with the latest version of Licq.
/Erik
--- End Message ---
