239677 - nsCOMPtr_base bus error when opening new tab

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Ade Fewings]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040210 Firefox/0.8
Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.6) Gecko/20040116

After having just browsed to the opening page of a Horde webmail [e.g.
webmail.bangor.ac.uk, webmail.informatics.bangor.ac.uk], pressing Ctrl-T to open
a new tab causes a complete Mozilla crash with 'Bus Error' cited.  According to
the stack trace, the problem is in nsCOMPtr_base, see attachment.

Reproducible: Always
Steps to Reproduce:
1. Browse to Horde webmail opening page.
2. Press Ctrl-T for new tab.

Actual Results:  
Mozilla exit and 'Bus Error'

Expected Results:  
Kept working.

Solaris 9, GTK 1.2.10.

Comment 1

[Ade Fewings]

Attachment: Crash Stack Trace

Comment 2

[Roland Mainz]

Reporter:
From which URL did you download your FireFox 0.8 binary (exact URL, please) ?

Comment 3

[Ade Fewings]

See from the above Build Identifier that it's not Firefox that is crashing - i
was unable to replicate the bug with Firefox.  The Mozilla build concerned is
1.6, but i can't remember which of the three versions on mozilla.org that i
downloaded.  I think it was the GTK build, but i'm not certain.  The build
details are as follows, if that helps:

about:buildconfig

Build platform
target
sparc-sun-solaris2.8

Build tools
Compiler 	Version 	Compiler flags
/opt/SUNWspro/bin/cc 	Sun C 5.5 Patch 112760-04 2003/10/03 	-xstrconst
-xbuiltin=%all -mt
/opt/SUNWspro/bin/CC 	Sun C++ 5.5 Patch 113817-03 2003/10/14 	-xbuiltin=%all -mt
-I/usr/openwin/include

Configure arguments
--enable-default-toolkit=gtk2 --enable-optimize=-xO2 --disable-postscript
--enable-ctl --enable-image-decoders=all --enable-calendar --enable-svg
--enable-extensions=all --enable-crypto --disable-tests --disable-debug
--without-system-nspr --without-system-zlib --without-system-jpeg
--without-system-png --without-system-mng

Comment 4

[Roland Mainz]

I can't reproduce the problem with
http://ftp.mozilla.org/pub/mozilla.org/mozilla/releases/mozilla1.6/contrib/mozilla-sparc-sun-solaris2.8-1.6.tar.gz
(BTW: That build was updated few weeks ago with a new version compiled with a
newer compiler version) - I have tried to browse http://webmail.bangor.ac.uk and
http://webmail.informatics.bangor.ac.uk with other pages like
http://www.heise.de etc. in other tabs.

Reporter:
Two questions:
- Does the problem occur after you login into the Horde webmail system (note: I
do not have an account, making testing more difficult)
- Do you have all Solaris 2.9/SPARC patches listed in
http://lxr.mozilla.org/seamonkey/source/xpfe/bootstrap/init.d/moz_patch_checker.dtksh#84
installed in your system ?

Comment 5

[Ade Fewings]

I'm missing a couple of those patches to the correct revision level.  Let me try
fixing that and also the new build and see what happens.

BTW, you don't need to be logged into Horde, it just needs to be there.

I'll get back once tried.

Comment 6

[Ade Fewings]

Have installed relevant Sun patches and the newer build of Mozilla and this
appears to have fixed the problem.  Apologies for raising it in the first place
- if i had known of that list of additional patches required, i would obviously
have looked before posting the bug.  Thanks for your time.

Comment 7

[Roland Mainz]

Ade Fewings wrote:
> Have installed relevant Sun patches and the newer build of Mozilla and this
> appears to have fixed the problem.  Apologies for raising it in the first 
> place - if i had known of that list of additional patches required, i would 
> obviously have looked before posting the bug. 

I know what you mean... finally I decided to fix the problem with bug 230598
("RFE: Add Solaris patchchecker to Mozilla"). This feature will automagically
check patch dependicies in future (e.g. >= release 1.7a) version of Mozilla.

Additionally there are the release notes for Solaris (see
http://www.mozilla.org/releases/mozilla1.7b/installation-ports.html#ports_solaris)
but they were not updated yet (the automated patch checker was more important
but it's on my ToDo list to update the WWW docs).

> Thanks for your time.

No problem :)