Escalated to Bugzilla from IssueTracker
Event posted on 18-06-2009 02:31pm IST by spoyarek Description of problem: Base OS: RHEL-5.3 Problem Component: libgtop2 Fix for the following bugzilla results in a number of warnings and incorrect values for memory utilization for processes in gnome-system-monitor: https://bugzilla.redhat.com/show_bug.cgi?id=443749 This adds an extra entry for Swap in smaps, thus breaking the parsing logic in libgtop2. Related upstream bug: http://bugzilla.gnome.org/show_bug.cgi?id=518145 How reproducible: Always. Steps to Reproduce: Start gnome-system-monitor from gnome-terminal Actual results: Warnings as seen in the attached file Expected results: No such warnings :) Additional info: Attached patch is a combination of a few patches to upstream libgtop: http://svn.gnome.org/viewvc/libgtop/trunk/sysdeps/linux/procmap.c?r1=2598&r2=2610&view=patch http://svn.gnome.org/viewvc/libgtop/trunk/sysdeps/linux/procmap.c?r1=2673&r2=2713&view=patch http://svn.gnome.org/viewvc/libgtop/trunk/sysdeps/linux/glibtop_private.c?r1=2637&r2=2713&view=patch This seems to fix the issue. I have given a test package to the customer. Will revert with his response. Revision 2610 is not exactly relevant to this (not tested without it) but I thought it would be a good idea to get this in too :) This event sent from IssueTracker by rkhadgar [Support Engineering Group] issue 308652
Created attachment 349142 [details] patch based on upstream code
RE: "This seems to fix the issue. I have given a test package to the customer. Will revert with his response." Did we ever hear back from the customer on this, whether the proposed patch set fixed their issue or not?
Resetting to NEW because there is no 5.4.z flag.