After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 427498 - crash in System Monitor: Checking my System Monit...
crash in System Monitor: Checking my System Monit...
Status: RESOLVED DUPLICATE of bug 354559
Product: system-monitor
Classification: Core
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2007-04-08 05:46 UTC by snyper64
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description snyper64 2007-04-08 05:46:15 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Checking my System Monitor to see why I had such a high load on my CPU when i was just in desktop.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 157409280 vsize: 157409280 resident: 19722240 share: 13586432 rss: 19722240 rss_rlim: -1
CPU usage: start_time: 1176010949 rtime: 221 utime: 133 stime: 88 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 47291800370000 (LWP 30850)]
(no debugging symbols found)
0x00002b02f8c0ceb5 in waitpid () from /lib/libpthread.so.0

+ Trace 125966

Thread 1 (Thread 47291800370000 (LWP 30850))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_tree_model_get_valist
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 gtk_tree_model_get
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #5 sexy_tree_view_new
    from /usr/lib64/libsexy.so.2
  • #6 ??
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


palfrey





          2007-04-08 11:54:08 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?

*** This bug has been marked as a duplicate of 354559 ***