GNOME Bugzilla – Bug 440360
crash in System Monitor: just accessed the progra...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? just accessed the program after it was running for a day or two Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 154767360 vsize: 0 resident: 154767360 share: 0 rss: 131280896 rss_rlim: 0 CPU usage: start_time: 1179196967 rtime: 0 utime: 522390 stime: 0 cutime:492705 cstime: 0 timeout: 29685 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/gnome-system-monitor' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1225405952 (LWP 5711)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 135462
Thread 1 (Thread -1225405952 (LWP 5711))
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 352444 ***