Comment 6 for bug 343588

Hey Musthafa,

I am sorry to disappoint you, but we really don't see an error here.
The memory doesn't seem to be off much for most apps and a bit more for X, but in general it is what top spits out, so no issue to be spotted there.
As for the CPU values: a) technically a CPU load value changes every few nano seconds, so it is very much up to the application when to count the value b) when you are viewing the graphs, they will themselfs put some more load on the CPU, even if you click very fast between table and graphs, the actual tab switch puts extra load on the CPU, so the values will be quite different each time.

If you can show a bit more precise values where the memory is off a lot (X is not much accountable for, since virtually every application shares memory with X, and leaves a memory footprint in X's cached memory as well), please reopen this bug report and post the information.

For now I am closing this bug as invalid.

None the less, I wish you a very nice day and thank you for this report :)