Bug 189507

Summary:	ksysguard reports negative memory usage
Product:	[Unmaintained] ksysguard	Reporter:	Dat Nhan <roongxkhoong>
Component:	general	Assignee:	KSysGuard Developers <ksysguard-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	lotusom-dev, mail, rlerallut
Priority:	NOR
Version:	4.7 and older
Target Milestone:	---
Platform:	unspecified
OS:	Other
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	Screenshot showing negative value for physical memory amount (in kbytes)

Description Dat Nhan 2009-04-13 08:08:00 UTC

Version:           4 (using KDE 4.1.2)
OS:                I Don't Know
Installed from:    I Don't Know

I am running Fedora 10. When I run a program that uses 2.3GiB (report by GNome system monitor), but ksysguard reports -1,783M (negative).

Comment 1 Sebastien Martel 2009-07-21 20:00:25 UTC

Is this still an issue?  Which memory sensor was reporting a negative value free/used/buffer/...?

Comment 2 Romain 2009-08-07 11:32:24 UTC

Created attachment 35957 [details]
Screenshot showing negative value for physical memory amount (in kbytes)

Comment 3 Romain 2009-08-07 11:32:51 UTC

I have the same problem on 4.3 (debian unstable) I'm attaching a screenshot.

It's the "Memory" sensor (tooltip says something like "This is the amount of real physical memory that this process is using by itself"). The Virtual sensor shows the proper value.

When display is in kilobytes, the number is negative (see screenshot). When it's in megabytes, the value is 0.1M and when it's in gigabyte it's 0.1G.

Hope this helps,
Romain

Comment 4 Mykola Krachkovsky 2009-09-26 17:40:02 UTC

KDE4.3.1 - same bug. Seems like ksysguard (or sensor) uses 32 bit _signed_ variable to keep process memory usage.

Comment 5 Julian Steinmann 2018-02-22 12:56:47 UTC

Cannot reproduce with KSysguard 5.12.1. Seems fixed.