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 548755 - crash in Epiphany Web Browser: control++
crash in Epiphany Web Browser: control++
Status: RESOLVED DUPLICATE of bug 525357
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-08-20 21:57 UTC by polo74
Modified: 2008-08-20 22:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description polo74 2008-08-20 21:57:59 UTC
Version: 2.22.3

What were you doing when the application crashed?
control++ 


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-486 #1 Fri Jul 18 17:03:35 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 188715008 vsize: 188715008 resident: 68132864 share: 27697152 rss: 68132864 rss_rlim: 4294967295
CPU usage: start_time: 1219266971 rtime: 6536 utime: 6038 stime: 498 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b5b700 (LWP 5611)]
[New Thread 0xb1574b90 (LWP 5734)]
[New Thread 0xb1dffb90 (LWP 5731)]
[New Thread 0xb37bab90 (LWP 5714)]
[New Thread 0xb2fb9b90 (LWP 5619)]
[New Thread 0xb408ab90 (LWP 5617)]
[New Thread 0xb508cb90 (LWP 5616)]
[New Thread 0xb488bb90 (LWP 5615)]
[New Thread 0xb5af4b90 (LWP 5612)]
(no debugging symbols found)
0xb7f32430 in __kernel_vsyscall ()


----------- .xsession-errors (2432 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
--------------------------------------------------
Comment 1 Reinout van Schouwen 2008-08-20 22:29:11 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 525357 ***