Closed
Bug 208023
Opened 22 years ago
Closed 22 years ago
After installing RC1, launching Mozilla results in unhandled exception (before splash screen)
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: msherman, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla RC 1
I installed 1.4 RC1 using the provided Windows installer. Upon double-clicking
the resulting shortcut on my desktop I get an unhandled exception (memory could
not be "read"). Mozilla will therefore not start up. I went back to install an
older 1.4 Beta and the same problem showed up. 1.4 Beta used to work fine. It
looks like the RC 1 installer may have corrupted something. I had to go back to
1.3.1 to get a working version, but even that on startup warns be about a
missing xpcom_compat.dll.
Reproducible: Always
Steps to Reproduce:
1. install mozilla 1.4 rc1 on windows 2000
2. double-click shortcut icon on desktop
Actual Results:
crash (unhandled exception)
Expected Results:
mozilla should have started up
Comment 1•22 years ago
|
||
have you deleted the old installation? else this is another dup of Bug 123907
Reporter | ||
Comment 2•22 years ago
|
||
Yes, I removed my old installation. I then installed 1.4 RC1. It is not a dup
of bug 123907, as this one is rather more critical than just being annoying.
After installation, Mozilla crashes on startup. I cannot run Mozilla. I do not
even see the splash screen.
Reporter | ||
Comment 3•22 years ago
|
||
Note: I ran the uninstaller. I did *not* manually delete the c:\program
files\mozilla.org\ directory. Do you happen to know where Mozilla Mail stores
e-mail? I would be more than happy to just wipe the program files\mozilla.org
dir if I knew my mail would remain intact. Thanks!
Your mail and profile info is in the Documents and Settings directory. This is
left on uninstall. So it's perfectly safe (and a good idea) to delete the
mozilla program directory.
Doing some triage. Is this bug still an issue on newer builds? It WFM using the
20030908 build. This looks like a potential WORKSFORME or INVALID at this point
since it's on an ancient build.
no response in over 3 months ...
-> WFM
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•