Closed Bug 24316 Opened 25 years ago Closed 25 years ago

[PP]Linux only: Show a bug report in seamonkey crashes application

Categories

(SeaMonkey :: General, defect, P3)

Other
Linux
defect

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: fenella, Assigned: trudelle)

References

Details

(Keywords: crash)

Linux Redhat 6.0 (2000-01-18-11 M13)
Steps:
1. Launch browser
2. Enter: http://bugzilla.mozilla.org to display the Bugzilla page
3. Enter a bug number and click Show

Actual result: Browser crashes

Here is the error shown in the console window
Document http://bugzilla.mozilla.org/ loaded successfully
Document: Done (1.035 secs)
! nsSecureBrowserUIImpl found: http://bugzilla.mozilla.org/
change lock icon to unlock ?(http 0)
WEBSHELL+ = 6
change lock icon to unlock - new document
WEBSHELL- = 5
title string = [Bugzilla bug 14905 - Mozilla]

Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkObject'
warning: attempted to CreateNative() without a superwin parent

Expected result: it should display the bug report

This only occurs on Linux only, it is a parity bug.
Assignee: phil → don
Component: Back End → Browser-General
Product: MailNews → Browser
Reassign to don, change product and component
QA Contact: lchiang → gerardok
*** Bug 24313 has been marked as a duplicate of this bug. ***
Copying a comment made by zach@math.berkeley.edu in bug 24313:

******* Additional Comments From zach@math.berkeley.edu  2000-01-18 20:18
I also get this, on Linux build 2000.01.18.11.  I got it when searching at
dmoz.  Put in search terms, click serach, segfault.  Here's the trace:

WEBSHELL+ = 4
WEBSHELL- = 3
title string = [Open Directory - Search Results - Mozilla]

Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkObject'
warning: attempted to CreateNative() without a superwin parent

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1270]

Program received signal SIGSEGV, Segmentation fault.
0x411d86be in nsWindow::CreateNative ()
(gdb) where
#0  0x411d86be in nsWindow::CreateNative ()
#1  0x411d3f5c in nsWidget::CreateWidget ()
#2  0x411d40df in nsWidget::Create ()
#3  0x4096c06b in NSGetModule ()
#4  0x40970397 in NSGetModule ()
#5  0x40b2ed23 in NSGetModule ()
#6  0x40b2e9eb in NSGetModule ()
#7  0x40bed8dc in NSGetModule ()
#8  0x40bec86f in NSGetModule ()
#9  0x40be921e in NSGetModule ()
#10 0x40c9e5ce in NSGetModule ()
#11 0x40b1dab1 in NSGetModule ()
#12 0x40b9e331 in NSGetModule ()
#13 0x40b9db09 in NSGetModule ()
#14 0x406b1be3 in NSGetModule ()
#15 0x406b2066 in NSGetModule ()
#16 0x406afc90 in NSGetModule ()
#17 0x406b0402 in NSGetModule ()
#18 0x406af5da in NSGetModule ()
#19 0x406af14d in NSGetModule ()
#20 0x406b9db2 in NSGetModule ()
#21 0x406b9c97 in NSGetModule ()
#22 0x406ba420 in NSGetModule ()
#23 0x404b1e9b in NSGetModule ()
#24 0x40405123 in NSGetModule ()
#25 0x4047642f in NSGetModule ()
#26 0x40431903 in NSGetModule ()
#27 0x40431240 in NSGetModule ()
#28 0x4012ec17 in PL_HandleEvent ()
#29 0x4012eb86 in PL_ProcessPendingEvents ()
#30 0x400f5c4a in nsEventQueueImpl::ProcessPendingEvents ()
#31 0x411c2bbf in nsAppShell::SetDispatchListener ()
#32 0x411c298d in keysym2ucs ()
#33 0x4085552a in g_io_unix_dispatch ()
#34 0x40856be6 in g_main_dispatch ()
#35 0x408571a1 in g_main_iterate ()
#36 0x40857341 in g_main_run ()
#37 0x4077c859 in gtk_main ()
#38 0x411c307a in nsAppShell::Run ()
#39 0x41186c12 in nsAppShellService::Run ()
#40 0x804a3a5 in JS_PushArguments ()
#41 0x804a714 in JS_PushArguments ()
#42 0x40213cb3 in __libc_start_main (main=0x804a538 <JS_PushArguments+4848>,
    argc=1, argv=0xbffff864, init=0x8048fd8 <_init>, fini=0x804bae0 <_fini>,
    rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffff85c)
    at ../sysdeps/generic/libc-start.c:78
Assignee: don → trudelle
Peter, can Pav take a look at this one?
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Both of these sets of steps work fine for me, using today's opt comm bits
(2000011908) on RH 6.1.  resolving as wfm, if anyone still sees this, please
reopen with sufficient steps to reproduce.
Adding crash keyword
Keywords: crash
Linux (2000-07-11-13 M17)
I have not seen this problem for a while. Verified it.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.