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 540323 - crash in Epiphany Web Browser: closing the browser
crash in Epiphany Web Browser: closing the browser
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-26 13:58 UTC by gms8994
Modified: 2008-06-27 11:08 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description gms8994 2008-06-26 13:58:44 UTC 
Version: 2.22.2

What were you doing when the application crashed?
closing the browser


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-bigmem #1 SMP Thu Jun 12 17:11:59 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: SphereCrystal

Memory status: size: 130129920 vsize: 130129920 resident: 55828480 share: 26427392 rss: 55828480 rss_rlim: 4294967295
CPU usage: start_time: 1214488388 rtime: 704 utime: 663 stime: 41 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6b9f720 (LWP 27306)]
0xb7f71424 in __kernel_vsyscall ()

+ Trace 201449

Thread 1 (Thread 0xb6b9f720 (LWP 27306))

  • #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 ??
  • #8 NS_HasPendingEvents_P
    at nsThreadUtils.cpp line 207
  • #9 nsBaseAppShell::OnProcessNextEvent
    at nsBaseAppShell.cpp line 288
  • #10 nsThread::ProcessNextEvent
    at nsThread.cpp line 497
  • #11 NS_ProcessPendingEvents_P
    at nsThreadUtils.cpp line 180
  • #12 nsBaseAppShell::NativeEventCallback
    at nsBaseAppShell.cpp line 121
  • #13 nsAppShell::EventProcessorCallback
    at nsAppShell.cpp line 69
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #16 ??
  • #17 ??
    from /usr/lib/libglib-2.0.so.0
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (41809 sec old) ---------------------
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: your execibar value is not between 0 and 100, therefore it will be ignored
Conky: 
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-06-27 11:08:35 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 ***