GNOME Bugzilla – Bug 146836
Crashed when order by CPU load and change monitored processes
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Fedora Core release 2 (Tettnang) Package: gnome-applets Severity: normal Version: GNOME2.6. 2.5.x Gnome-Distributor: Red Hat, Inc Synopsis: Crashed when order by CPU load and change monitored processes Bugzilla-Product: gnome-applets Bugzilla-Component: cpuload Bugzilla-Version: 2.5.x BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Using version 2.6.0, the program crashed when I had enabled the '% CPU' column and then tried to order by this column, with 'All Processes' selected. Steps to reproduce the crash: 1. Preferences > Enable '% CPU' monitoring. 2. Order by '% CPU' column. 3. Use the selector in top-right to change which processes to monitor Expected Results: Application crashes suddenly. How often does this happen? Every time I try it. Additional Information: Using version 2.6.0 Debugging Information: Backtrace was generated from '/usr/bin/gnome-system-monitor' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -151072640 (LWP 32453)] (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)...(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)...0x0024e402 in ?? ()
+ Trace 48203
Thread 1 (Thread -151072640 (LWP 32453))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 07:28 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gnome-applets". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was tunnie@uk2.net. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Reassigning to system-monitor.
Reassigning to gail based on the stack trace (kick me if I'm wrong). Note that the only other stack trace that appears to contain gail_tree_view_ref_focus_cell() in the stack trace is bug 138885.
This looks like a duplicate of bug 156831 to me. Unfortunately I cannot reproduce this one either. *** This bug has been marked as a duplicate of 156831 ***