Closed Bug 209936 Opened 21 years ago Closed 21 years ago

Crash on startup

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 200651

People

(Reporter: anthonyj, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030516 Mozilla Firebird/0.6
Build Identifier: http://ftp.mozilla.org/pub/mozilla/releases/mozilla1.4rc2/mozilla-win32-1.4rc2-installer.exe

I have been running mozilla in various flavours for 8 months.
Just upgraded from 1.4 RC1 to 1.4 RC2, and now am unable to startup.
I get a memory access violation in XPCOM.dll:
610F0736   mov         esi,610F3B40h
610F073B   push        610F6398h
610F0740   push        eax
610F0741   lea         ecx,[ebp+8]
610F0744   mov         dword ptr [ebp-10h],ebx
610F0747   mov         dword ptr [ebp-18h],esi
610F074A   mov         dword ptr [ebp+8],ebx
610F074D   call        610F0964
610F0752   lea         ecx,[ebp-14h]
610F0755   mov         dword ptr [ebp-18h],esi
610F0758   call        610F0932
610F075D   cmp         dword ptr [ebp+8],ebx
610F0760   je          610F0799
610F0762   mov         eax,dword ptr [edi+24h]
610F0765   cmp         eax,ebx
610F0767   je          610F0799
610F0769   mov         eax,dword ptr [eax]  <-- this line has the error



Reproducible: Always

Steps to Reproduce:
1.try to start mozilla
2.
3.
After uninstalling the previous version of Mozilla, was the program directory
for Mozilla empty?
Summary: Crash on startup → Crash on startup
No the directory was not empty.
I removed what was there, and reinstalled.
it now works.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---

*** This bug has been marked as a duplicate of 200651 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago21 years ago
Resolution: --- → DUPLICATE
This one should be duped to bug 195600, see bug 200651 comment 12.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.