Bug 427000 – crash in Epiphany Web Browser: Closing the window

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 427000 - crash in Epiphany Web Browser: Closing the window


Summary:	crash in Epiphany Web Browser: Closing the window


Status:	RESOLVED DUPLICATE of bug 413350

Product:	epiphany
Classification:	Core
Component:	General
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Epiphany Maintainers
QA Contact:	Marco Pesenti Gritti

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-06 17:24 UTC by joe
Modified:	2007-04-06 17:51 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description joe 2007-04-06 17:24:11 UTC

Version: 2.16.3

What were you doing when the application crashed?
Closing the window



Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2933.fc6 #1 SMP Mon Mar 19 11:00:19 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 561885184 vsize: 561885184 resident: 38727680 share: 23740416 rss: 38727680 rss_rlim: -1
CPU usage: start_time: 1175880219 rtime: 79 utime: 66 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912505715888 (LWP 9301)]
(no debugging symbols found)
0x0000003d1380d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 125553

Thread 1 (Thread 46912505715888 (LWP 9301))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 nsSupportsWeakReference::~nsSupportsWeakReference\$base
from /usr/lib64/firefox-1.5.0.10/libgtkembedmoz.so
#3 <signal handler called>
#4 ??
#5 PR_NewRWLock
from /usr/lib64/libnspr4.so
#6 PR_ProcessExit
from /usr/lib64/libnspr4.so
#7 PR_ProcessExit
from /usr/lib64/libnspr4.so
#8 __cxa_pure_virtual
from /usr/lib64/libnspr4.so
#9 ??
#10 _fini
from /usr/lib64/libnspr4.so
#11 ??
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (572 sec old) ---------------------
2007-04-06T17:14:17Z INFO: checkPacketInID: packet_out_of_order - got packet 1788 expecting 1771 from 64.129.40.43:12035
2007-04-06T17:14:18Z INFO: _queueDataRequest: Starting transfer for 4716ab75-4ef1-d2d2-34af-9b6c0b1eff31
2007-04-06T17:14:18Z INFO: processParcelProperties: out of order agent parcel sequence id 2 last good 3
2007-04-06T17:14:19Z INFO: processTransferInfo: Receiving 7beb70f6-461a-17f1-bf7e-7ec15ef78932, size 756 bytes
2007-04-06T17:14:21Z INFO: idle: Unknown object updates: 4
2007-04-06T17:14:21Z INFO: sendToSim: Sending throttle settings, total BW 500
2007-04-06T17:14:21Z INFO: updateDynamicThrottle: Tightening network throttle to 512000
2007-04-06T17:14:23Z INFO: startNextTransfer: Getting asset data for: f0f42e31-e219-eef0-53e5-65f9528631b4
2007-04-06T17:14:23Z INFO: _queueDataRequest: Starting transfer for f0f42e31-e219-eef0-53e5-65f9528631b4
2007-04-06T17:14:24Z INFO: processTransferInfo: Receiving 93db7ee6-b7bb-b358-dd1e-057fae986d9e, size 152146 bytes
2007-04-06T17:14:26Z INFO: idle: Unknown object updates: 2
2007-04-06T17:14:26Z INFO: sendToSim: Sending throttle settings, total BW 450
2007-04-06T17:14:26Z INFO: updateDynamicThrottle: Tightening network throttle to 460800
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 Pedro Villavicencio 2007-04-06 17:51:42 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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