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 357379 - crash in Epiphany Web Bookmarks: I just closed the browse...
crash in Epiphany Web Bookmarks: I just closed the browse...
Status: RESOLVED DUPLICATE of bug 354790
Product: epiphany
Classification: Core
Component: General
2.16.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Marco Pesenti Gritti
Depends on:
Blocks:
 
 
Reported: 2006-09-23 21:46 UTC by Farhad Shakiba
Modified: 2006-09-23 22:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Farhad Shakiba 2006-09-23 21:46:17 UTC
Version: 2.16.0

What were you doing when the application crashed?
I just closed the browser window to exit the application by clicking the X button. I had no tabs open at the time.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 149340160 vsize: 0 resident: 149340160 share: 0 rss: 54407168 rss_rlim: 0
CPU usage: start_time: 1159038713 rtime: 0 utime: 7486 stime: 0 cutime:7237 cstime: 0 timeout: 249 it_real_value: 0 frequency: 736

Backtrace was generated from '/usr/bin/epiphany'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228682720 (LWP 26689)]
[New Thread -1383101536 (LWP 31720)]
[New Thread -1349530720 (LWP 31719)]
[New Thread -1309643872 (LWP 28595)]
[New Thread -1266693216 (LWP 26693)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1228682720 (LWP 26689))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 gtk_moz_embed_get_title
    from /usr/lib/firefox/libgtkembedmoz.so
  • #4 <signal handler called>
  • #5 gtk_widget_destroy
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 NSGetModule
    from /usr/lib/firefox/components/libgkplugin.so
  • #7 NSGetModule
    from /usr/lib/firefox/components/libgkplugin.so
  • #8 ??
    from /usr/lib/firefox/components/libgkplugin.so
  • #9 ??
  • #10 ??
    from /usr/lib/firefox/components/libgklayout.so
  • #11 ??
  • #12 NSGetModule
    from /usr/lib/firefox/components/libgklayout.so
  • #13 NSGetModule
    from /usr/lib/firefox/components/libgklayout.so
  • #14 NSGetModule
    from /usr/lib/firefox/components/libgklayout.so
  • #15 NSGetModule
    from /usr/lib/firefox/components/libgkplugin.so
  • #16 NSGetModule
    from /usr/lib/firefox/components/libgkplugin.so
  • #17 ??
    from /usr/lib/firefox/components/libgkplugin.so
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 PR_Unlock
    from /usr/lib/libnspr4.so
  • #22 ??
    from /usr/lib/firefox/components/libgkplugin.so
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
    from /usr/lib/firefox/components/libgkplugin.so
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
    from /usr/lib/firefox/components/libgkplugin.so
  • #31 ??
  • #32 ??
  • #33 ??
  • #0 __kernel_vsyscall

Comment 1 Reinout van Schouwen 2006-09-23 22:42:26 UTC
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Christian Persch 2006-09-23 22:56:19 UTC

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