After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 670816 - Memory column sorted incorrectly
Memory column sorted incorrectly
Status: RESOLVED DUPLICATE of bug 507108
Product: system-monitor
Classification: Core
Component: process list
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2012-02-26 01:56 UTC by maratbn
Modified: 2012-02-26 21:54 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
This screenshot shows incorrect sorting of the 'Memory' column. (125.69 KB, image/png)
2012-02-26 01:58 UTC, maratbn 		Details

Description maratbn 2012-02-26 01:56:03 UTC 
I tried to sort the list of processes by their memory usage, in descending order, by clicking on the 'Memory' column header.

The 'VirtualBox' process was using the most memory on my system at that time.  It initially appeared on top of the list, but then sank down under other processes that had a smaller memory usage.

This is on an Intel Core i7 system, running Ubuntu 11.10, and Gnome 3 in classic mode.
Comment 1 maratbn 2012-02-26 01:58:07 UTC 
Created attachment 208429 [details]
This screenshot shows incorrect sorting of the 'Memory' column.

Adding screenshot of the problem.
Comment 2 André Klapper 2012-02-26 10:46:53 UTC 
[Adding missing "QA Contact" entry so system monitor bug report changes can still be watched via the "Users to watch" list on https://bugzilla.gnome.org/userprefs.cgi?tab=email when the assignee is changed to an individual.]
Comment 3 Robert Roth 2012-02-26 21:54:39 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.

*** This bug has been marked as a duplicate of bug 507108 ***