GNOME Bugzilla – Bug 130746
Gnome system monitor aborted after running seven hours
Last modified: 2011-11-11 10:03:55 UTC
Package: system-monitor Severity: normal Version: 2.0.4 Synopsis: Gnome system monitor aborted after running seven hours Bugzilla-Product: system-monitor Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: System-monitor crashed while my system was running unattended. I had left system-monitor running because I had just added spamd to postfix, and spamd processes appear to be consuming 94-97% of CPU cycles (while postfix stays busy, procmail, and thus spamc, only gets called perhaps 30 times an hour). Steps to reproduce the problem: 1. Haven't tried this yet, but will restart system-monitor without changing anything else 2. 3. Actual Results: Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-system-monitor' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 1086391200 (LWP 22414)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...0xffffe002 in ?? ()
+ Trace 43053
Thread 1 (Thread 1086391200 (LWP 22414))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-01-06 23:27 ------- Reassigning to the default owner of the component, kfv101@psu.edu.
Maybe a leak/loop on gtk_tree. Can you still reproduce this with newer versions of gtk+/gnome-system-monitor?
After a second crash, I stopped using the System Monitor. I have not tried upgrading from a newer source tree (didn't know there was one).
*** This bug has been marked as a duplicate of 98295 ***