201883 - crash at startup

Status: RESOLVED INVALID

(SeaMonkey :: General, defect)

Description

[Paul Ward]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312

1.4a and latest nightly build as of 2003/04/13 crash at startup 

Reproducible: Always

Steps to Reproduce:
1. start mozilla
2.
3.

Actual Results:  
Crash even before splash screen appears


MOZILLA caused an invalid page fault in
module XPCOM.DLL at 016f:61e40b2e.
Registers:
EAX=4d7a6f6d CS=016f EIP=61e40b2e EFLGS=00010202
EBX=00000000 SS=0177 ESP=0065f61c EBP=0065f640
ECX=007841e4 DS=0177 ESI=61e44b40 FS=0ec7
EDX=317b0fff ES=0177 EDI=00788430 GS=0000
Bytes at CS:EIP:
8b 00 3b c3 74 21 33 f6 80 38 00 74 1a 8b 4d 08 
Stack dump:
00000000 80000000 00785c60 61e44b40 007841c0 00000000 00000001 007841c8 00000000
0065faa0 61e27a7f 00785c64 007841c0 00789fa0 0078dc00 61e4707c

Comment 1

[Boris Zbarsky [:bzbarsky]]

The numeric stack dump is not very useful... is there a talkback incident ID?

Comment 2

[Paul Ward]

Talkback is on, but does not activate after crash.

Comment 3

[Hermann Schwab]

build of 2003/04/13 is broken, have a look at bug 201889 and it´s links.
I´m using nightlies regularly, and didn´t have problems with last weeks nightly
before 04/13, but 2003041304 and 2003041308 didn´t start on my computer,
and when I went back to 2003041204 and installed it without previous deinstall,
i got a crash after about 15 minutes of downloading, that is about half the size
of a mozilla nightly. So if you installed ontop of the buggy 04/13, crashes
could be normal.

Comment 4

[David Balch]

The couple of builds since 1.4 that I've tried have crashed my dual proc
WinNT4sp6 machine. No splash, no Talkback.

I last tried 20030425 and it crashed, however, it runs fine on a collegue's dual
proc WinNT4sp6 machine :-/

I'll attach a DrWatson crash log from my machine.

Comment 5

[David Balch]

Attachment: NT4 crash log

Log from DrWatson on NT4, points to error in NS_NewGenericFactory (line 146)

Hopefully there's nothing incriminating in the rest of the log ;-)

Comment 6

[Billy Newsom]

I had same issue on Windows 2000, Mozilla 1.4b.  Try removing the old 1.3 spell 
checker.  See my comments on another bug 203670, which happens to be the same 
bug, just a different platform.  The key is to look for problems in 
NS_NewGenericFactory -- this is the actual keyword I searched for to find this 
bug and the one I commented on: bug 203670.  It will probably boil down to a 
few files, probably spell*.xpt or maybe spell*.dll

I guess I should have commented on an uncomfirmed bug, and not a closed one, 
but oh well.

See my recommended addition to the RELEASE NOTES for 1.4:
***
Please uninstall or delete any old Spell Checker Plugins prior to installing 
Mozilla 1.4.  Incompatibilities may cause Mozilla 1.4 to crash on startup.  
Look for them in the components subdirectory of Mozilla.  Known problems with:
spellchecker.xpt
spellchk.dll
***

Comment 7

[Noel St. John]

myspell.dll apparently is another spell checker file that must be deleted to
avoid the crash.  I had the exact same problem with Win98 installing 1.4.

This really should be in the installation notes!!!


-Noel

Comment 8

[Billy Newsom]

Dup of bug 205277?  It just got marked dupe of Bug 195600.  Is the reporter
still watching this bug?  This one still looks a lot like Bug 205277 except
maybe a Win98 flavor.  XPCOM.DLL is the same file in NT/2000, and it seems to
crash similarly.  See bug 210731, which is a way to keep this stuff from
happening for users who can't read the part of the Release notes that tell you
to always do a clean install of Mozilla into an empty directory.

Comment 9

[Noel St. John]

"See bug 210731, which is a way to keep this stuff from
happening for users who can't read the part of the Release notes that tell you
to always do a clean install of Mozilla into an empty directory."

It appears only the Linux install notes give that advice.  (Didn't read that? ;-)


-Noel

Comment 10

[Andreas Kunz]

Paul, David: can you reproduce this with current Mozilla builds?
Have you/had you spell checker or other extensions installed when this happen(s/ed)?

Comment 11

[Paul Ward]

No problems after uninstalling older version of Spell Checker and installing
newer version as suggested in comment #6.

Problem is resolved as far as I am concerned.

Comment 12

[Andreas Kunz]

Ok, thanks. Resolving the same way as all the other spell checker
incompatibility crashes were resolved.