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 538377 - crash in Epiphany Web Bookmarks: I closed the application
crash in Epiphany Web Bookmarks: I closed the application
Status: RESOLVED DUPLICATE of bug 509083
Product: epiphany
Classification: Core
Component: [obsolete] BugBuddyBugs
2.22.x
Other All
: High critical
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-06-14 21:44 UTC by bbfk
Modified: 2008-06-14 21:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description bbfk 2008-06-14 21:44:03 UTC 
Version: 2.22.2

What were you doing when the application crashed?
I closed the application


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Tue May 27 15:38:35 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: gnome

Memory status: size: 259473408 vsize: 259473408 resident: 175263744 share: 31105024 rss: 175263744 rss_rlim: 4294967295
CPU usage: start_time: 1213435064 rtime: 483265 utime: 475913 stime: 7352 cutime:2748 cstime: 533 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6ab0720 (LWP 16580)]
0xb7f25424 in __kernel_vsyscall ()

+ Trace 200457

Thread 1 (Thread 0xb6ab0720 (LWP 16580))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 nsProfileLock::FatalSignalHandler
    at nsProfileLock.cpp line 216
  • #6 <signal handler called>
  • #7 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 207
  • #8 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #9 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #10 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #11 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #12 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
    from /usr/lib/libglib-2.0.so.0
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (1385 sec old) ---------------------
**** alsa_pcm: xrun of at least 1213422884618.240 msecs
**** alsa_pcm: xrun of at least 1213422884618.240 msecs
**** alsa_pcm: xrun of at least 1213422884618.240 msecs
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-06-14 21:51:02 UTC 
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 bug has been marked as a duplicate of 509083 ***