GNOME Bugzilla – Bug 438625
crash in GNOME System Monitor: After more than 8 hours ...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? After more than 8 hours System Monitor crashed. I left my gnome session opened since yesterday. Now that I arrived at office I tried to restore System Monitor from the taskbar and it simply crashed and the Bug reporting tool was opened. Distribution: openSUSE 10.2 (X86-64) Gnome Release: 2.16.1 2006-11-28 (SUSE) BugBuddy Version: 2.16.0 Memory status: size: 370491392 vsize: 370491392 resident: 144138240 share: 9347072 rss: 153485312 rss_rlim: 1785364480 CPU usage: start_time: 1179179670 rtime: 517518 utime: 275644 stime: 241874 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/opt/gnome/bin/gnome-system-monitor' (no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47319463640768 (LWP 19102)] 0x00002b096a900c25 in waitpid () from /lib64/libpthread.so.0
+ Trace 134301
Thread 1 (Thread 47319463640768 (LWP 19102))
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 ***