FS#25258 - conky's mem_vsize and mem_res results of top are wrong

Attached to Project: Arch Linux
Opened by Peter Hercek (phercek) - Monday, 25 July 2011, 16:51 GMT
Last edited by Gaetan Bisson (vesath) - Monday, 25 July 2011, 18:01 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Conky's ${top mem_vsize ?} and ${top mem_res ?} do not report correct memory sizes for processes which take more than 4GiB of ram.

I reported this upstream too an proposed a patch:
https://sourceforge.net/tracker/?func=detail&aid=3366272&group_id=143975&atid=757310
(id: 3366272; title: mem_vsize and mem_res results of top are wrong)

I have also a patch for conky 1.8.1 (used by archlinux and the last released version as of now) which fixes the problem and is tested (contrary to the git version where I guessed the fix).

I'm posting since conky's maintainer may want to release new pkrel. If not, just disregard this.

Additional info:
* package version(s): extra/conky 1.8.1-3
* config and/or log files etc.
e.g. lines like these in .conkyrc will show the error
${top name 1} ${top pid 1} ${top cpu 1} ${top mem_vsize 1}


Steps to reproduce:
Just use ${top mem_vsize ?} or ${top mem_res ?} and create a process which uses more than 4GiB of RAM. Look how it is reported in conky. The size is cut to 32 bit which is rather confusing.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Monday, 25 July 2011, 18:01 GMT
Reason for closing:  Upstream
Comment by Gaetan Bisson (vesath) - Monday, 25 July 2011, 18:01 GMT
Since it is not a critical bug, I would rather wait for it to be fixed upstream.
But thanks for reporting and good luck with upstream (seems to be quite inactive lately).

Loading...