GNOME Bugzilla – Bug 382454
crash in System Monitor: Dodgy performance testin...
Last modified: 2011-11-11 10:03:55 UTC
Version: 2.16.1 What were you doing when the application crashed? Dodgy performance testing based on Sivan Greenberg`s post "Surely not a way to do performance testing" on planet.ubuntu.com, running "find /" in 6 tabs within a gnome-terminal. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 148258816 vsize: 148258816 resident: 18182144 share: 12177408 rss: 18182144 rss_rlim: -1 CPU usage: start_time: 1165280158 rtime: 739 utime: 475 stime: 264 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/gnome-system-monitor' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47274264664912 (LWP 8882)] (no debugging symbols found) 0x00002afee38b1eb5 in waitpid () from /lib/libpthread.so.0
+ Trace 91649
Thread 1 (Thread 47274264664912 (LWP 8882))
*** This bug has been marked as a duplicate of 354559 ***