Bug 118571 – trying to open a new page

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 118571 - trying to open a new page


Summary:	trying to open a new page


Status:	RESOLVED DUPLICATE of bug 107007

Product:	galeon
Classification:	Deprecated
Component:	Mozilla interaction
Version:	unspecified
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Philip Langdale
QA Contact:	Yanko Kaneti

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2003-07-29 12:55 UTC by Marius Lund Larsen
Modified:	2004-12-22 21:47 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Marius Lund Larsen 2003-07-29 12:55:43 UTC

Package: galeon
Severity: normal
Version: 1.3.7
Synopsis: trying to open a new page
Bugzilla-Product: galeon
Bugzilla-Component: Mozilla interaction
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Open up alot of pages in tabs, and it died.

Steps to reproduce the problem:
1.Open up my bank (http://www.nor.no), the phone company
(http://www.telenor.no), my hospital (http://www.smerteklinikken.com).
And used the pages.
2. And suddenly it died.

 

Actual Results:
it died

Expected Results:


How often does this happen?

This is the first time
Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/galeon-bin'

(no debugging symbols found)...[New Thread 1088914432 (LWP 2918)]
[New Thread 1129594160 (LWP 2939)]
[New Thread 1155792176 (LWP 2934)]
[New Thread 1137986864 (LWP 2925)]
[New Thread 1116949808 (LWP 2923)]
[New Thread 1107262768 (LWP 2922)]
0xffffe002 in ?? ()

+ Trace 39113

Thread 1 (Thread 1088914432 (LWP 2918))

#0 ??
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 nsProfileLock::FatalSignalHandler(int)
from /usr/lib/mozilla-1.4/libgtkembedmoz.so
#3 <signal handler called>
#4 gtk_widget_get_toplevel
from /usr/lib/libgtk-x11-2.0.so.0
#5 gtk_false
from /usr/lib/libgtk-x11-2.0.so.0
#6 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gdk_events_queue
from /usr/lib/libgdk-x11-2.0.so.0
#8 g_get_current_time
from /usr/lib/libglib-2.0.so.0
#9 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#10 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#11 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#12 bonobo_main
from /usr/lib/libbonobo-2.so.0
#13 main
#14 __libc_start_main
from /lib/tls/libc.so.6
#0 ??





------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-07-29 08:55 -------

Unknown version 1.3.x in product galeon. Setting version to the default, "unspecified".
The original reporter (trench@trench.no) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, philipl@mail.utexas.edu.

Comment 1 Elijah Newren 2003-07-29 18:14:25 UTC

Thanks for the bug report.  This particular bug has already been
reported into our bug tracking system, but no one has provided a stack
trace with debugging details.  If you have enough time and ability,
could you could recompile gtk with debugging info turned on (using the
'-g' flag)?  If you are using Red Hat 9, you can simply install
  http://people.redhat.com/otaylor/tmp/gtk2-debuginfo-2.2.1-4.i386.rpm
instead of doing any recompiling.  Then simply continue submitting any
bug reports you get--hopefully one of them will be a duplicate of this
"random gtk crasher" bug and will provide us with the debugging
symbols we need.

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