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 539207 - crash in Epiphany Web Browser: Loading bugzilla.gnome.o...
crash in Epiphany Web Browser: Loading bugzilla.gnome.o...
Status: RESOLVED DUPLICATE of bug 535883
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-20 00:34 UTC by pbloomfield
Modified: 2008-06-20 11:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description pbloomfield 2008-06-20 00:34:29 UTC 
Version: 2.22.2

What were you doing when the application crashed?
Loading bugzilla.gnome.org


Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.2 2008-05-28 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.6-55.fc9.i686 #1 SMP Tue Jun 10 16:27:49 EDT 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10499902
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 156672000 vsize: 156672000 resident: 38649856 share: 21438464 rss: 38649856 rss_rlim: 4294967295
CPU usage: start_time: 1213921909 rtime: 372 utime: 361 stime: 11 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[?1034h[Thread debugging using libthread_db enabled]
[New Thread 0xb7f50730 (LWP 14533)]
[New Thread 0xb31b7b90 (LWP 14550)]
[New Thread 0xb3bb8b90 (LWP 14549)]
[New Thread 0xb45cbb90 (LWP 14540)]
[New Thread 0xb4fccb90 (LWP 14539)]
[New Thread 0xb59cdb90 (LWP 14538)]
[New Thread 0xb63ceb90 (LWP 14537)]
[New Thread 0xb6e1fb90 (LWP 14536)]
0x00110416 in __kernel_vsyscall ()

+ Trace 200890



----------- .xsession-errors (2037 sec old) ---------------------
Could not find the frame base for "IA__g_spawn_command_line_sync".
Could not find the frame base for "g_io_unix_dispatch".
Could not find the frame base for "g_main_context_iterate".
Could not find the frame base for "_pr_poll_with_poll".
Could not find the frame base for "pt_TimedWait".
Could not find the frame base for "pt_TimedWait".
Could not find the frame base for "start_thread".
Could not find the frame base for "start_thread".
Could not find the frame base for "pt_TimedWait".
Could not find the frame base for "pt_TimedWait".
Could not find the frame base for "pt_TimedWait".
Could not find the frame base for "pt_TimedWait".
Could not find the frame base for "PR_Wait".
Could not find the frame base for "start_thread".
Could not find the frame base for "IA__g_spawn_sync".
--------------------------------------------------
Comment 1 Peter Bloomfield 2008-06-20 11:51:11 UTC 
Bug #535883 seems to be the lead bug for this issue.  The stack traces are almost identical:

370:rv = mOwner->mFixup->CreateExposableURI (favUri, getter_AddRefs (exposableURI));

versus

433:rv = mOwner->mFixup->CreateExposableURI (docUri, getter_AddRefs (exposableURI));


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