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 65615 - "crash detected" window on closing
"crash detected" window on closing
Status: RESOLVED DUPLICATE of bug 58977
Product: galeon
Classification: Deprecated
Component: User interface
unspecified
Other other
: Normal normal
: ---
Assigned To: Marco Pesenti Gritti
Yanko Kaneti
Depends on:
Blocks:
 
 
Reported: 2001-11-28 14:09 UTC by mike_b_laughton
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mike_b_laughton 2001-11-28 14:08:28 UTC
Package: galeon
Severity: minor
Version: 1.0
Synopsis: "crash detected" window on closing
Bugzilla-Product: galeon
Bugzilla-Component: User interface

Description:
During use, the application worked great (nothing out of the ordinary).  Only after I closed Galeon did a Gnome crash window appear asking if I wanted to submit a bug report.

Immediately prior to closing I had been browsing in 3 tabs (one main window) all served from bigcharts.com and www2.marketwatch.com.  I issued 3 or 4 CTRL-W to close all of the tabs and the main window respectively, after which the crash window appeared.

And I don't know if this is normal, but I still have several galeon-bin processes running right now, even though I haven't restarted it (on a fresh boot ~30 min):

[mike@tabby mike]$ ps -eaf | grep galeon
mike      1241     1  2 07:54 ?        00:00:19 /usr/bin/galeon-bin
mike      1249  1241  0 07:54 ?        00:00:00 /usr/bin/galeon-bin
mike      1250  1249  0 07:54 ?        00:00:00 /usr/bin/galeon-bin
mike      1251  1249  0 07:54 ?        00:00:00 /usr/bin/galeon-bin
mike      1315  1249  0 07:56 ?        00:00:00 /usr/bin/galeon-bin

System:
Red Hat 7.2
Mozilla 0.9.6
Galeon 1.0

I have popup-windows disabled, if that makes any difference.


Debugging Information:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 1024 (LWP 1241)]
[New Thread 2049 (LWP 1249)]
[New Thread 1026 (LWP 1250)]
[New Thread 2051 (LWP 1251)]
[New Thread 13316 (LWP 1315)]

0x4080d669 in __wait4 () from /lib/i686/libc.so.6
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    at eval.c line 41
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #0 __wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 gnome_segv_handle
    at eval.c line 41
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #0 __strtol_internal
    at eval.c line 36




------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-11-28 09:08 -------

The original reporter (mike_b_laughton@yahoo.com) 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, mpeseng@tin.it.

Comment 1 Yanko Kaneti 2001-11-28 21:44:19 UTC

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