GNOME Bugzilla – Bug 122222
System monitor crashes when opening application (CPU intensive?)
Last modified: 2011-11-11 10:03:55 UTC
Package: system-monitor Severity: critical Version: 2.0.4 Synopsis: System monitor crashes when opening application (CPU intensive?) Bugzilla-Product: system-monitor Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: This happened in diferent situations, the last when opening a DivX movie in MPlayer. The System Monitor simply crashes. Steps to reproduce the problem: 1. Start System Monitor 2. Start some (CPU intensive ?) appliction 3. System Monitor crashes Actual Results: System Monitor crashes Expected Results: System Monitor keep running How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-system-monitor' (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)...[New Thread 1086382976 (LWP 6469)] (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)...0xffffe002 in ?? ()
+ Trace 40155
Thread 1 (Thread 1086382976 (LWP 6469))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-09-13 14:24 ------- The original reporter (ricardo.mota@sapo.pt) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, kfv101@psu.edu.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. This is a duplicate of bug 112249, which has been marked as a duplicate of 98295. *** This bug has been marked as a duplicate of 98295 ***