Bug 115874 – Crash while reproducing a bug

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 115874 - Crash while reproducing a bug


Summary:	Crash while reproducing a bug


Status:	RESOLVED DUPLICATE of bug 95238

Product:	system-monitor
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	System-monitor maintainers
QA Contact:	System-monitor maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-06-24 16:36 UTC by singularity
Modified:	2011-11-11 10:03 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description singularity 2003-06-24 16:36:54 UTC

Package: system-monitor
Severity: normal
Version: 2.0.4
Synopsis: Crash while reproducing a bug
Bugzilla-Product: system-monitor
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Gnome System Monitor crashed while I was reproducing an Epiphany Bug

Steps to reproduce the problem:
1. Reproduce this bug: http://bugzilla.gnome.org/show_bug.cgi?id=115873
2. 
3. 

I don't know whether this is consitently reproducible.

Actual Results:
Gnome System Monitor Crashed.

Expected Results:
Gnome System Monotir sholud have continued to monitor my system with no
interruptions.

How often does this happen?
First time since I upgraded to Red Hat 9. Gnome System Monotir
occasionally locked up completely when I was using the version supplied
with Red Hat 8.0.

Additional Information:
N/A



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)...[New Thread 1086398528 (LWP 25457)]
0xffffe002 in ?? ()

+ Trace 38138

Thread 1 (Thread 1086398528 (LWP 25457))

#0 ??
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 process_pixel
at pixops.c line 931
#4 pixops_process
at pixops.c line 1036
#5 pixops_scale
at pixops.c line 1657
#6 gdk_pixbuf_scale
at gdk-pixbuf-scale.c line 75
#7 gdk_pixbuf_scale_simple
at gdk-pixbuf-scale.c line 243
#8 pretty_table_get_icon
#9 remove_info_from_tree
#10 proctable_find_process
#11 proctable_update_list
#12 proctable_update_all
#13 cb_timeout
#14 g_main_context_wakeup
from /usr/lib/libglib-2.0.so.0
#15 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#16 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#17 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#18 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#19 gtk_main
at gtkmain.c line 1092
#20 main
#21 __libc_start_main
from /lib/tls/libc.so.6
#0 ??





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-06-24 12:36 -------

The original reporter (singularity@home.no) 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.

Comment 1 David Kennedy 2003-06-24 21:19:35 UTC


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