Closed Bug 195618 Opened 23 years ago Closed 23 years ago

Mozilla Browser 20030301xx crashes on startup

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
blocker

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 195600

People

(Reporter: gorgonz, Assigned: asa)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030221 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030221 coming from Build 2003022108, I installed the new Build 20030301xx. The implicite start and my manual start result in the same behaviour: Before the splash screen can be seen, mozilla crashes. It is told that a dump is done. Maybe You tell me, where to find it, so I can send it to You. Hint: Reinstall of 2003022108 makes everything fine again Reproducible: Always Steps to Reproduce: 1. 2. 3.
If you installed on top of an old version (rather than removing it first) then that's the problem and this is a dupe of the (invalid) bug 195600. This build *requires* a clean install.
xpcom.dll always crash, in previous release when u start a d/l. and now at startup... (clean install or not the old files are remplaced...)
Hi Jason, You are right. I did install on top of Build 20030221. Just aside of it, I did not know, that this new Build is already V1.4a . So, after uninstall AND deletion of old stuff, the browser will start again. Something that is completely new to me: no update installation allowed with mozilla (I always do update install since V1.2a ;-), just sometimes I'm told to delete somes .xul file). Though it is offtopic here, I risk a short question: How can I find out, whether a Latest Build is part of an actual beta-phase, that comes to an end soon, or is already part of the next alpha cycle? Is there a latest Build release note somewhere?
This is invalid, because installed on top of another version. Peter: Latest builds are always from the trunk. Sometimes the code is branched an the branch is then going through alpha and beta stages.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
v. dupe
Status: RESOLVED → VERIFIED
Reopening to resolve correctly, as per comment 3.
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 195600 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → DUPLICATE
.
Status: RESOLVED → VERIFIED
What is meant by a clean install? My usual procedure is to delete all of the files in the mozilla directory, except for the plugins directory, then install.over the reamins. I use the same .mozilla directory. Is the problem inthe plugins directory, or in the prefs file or both?
Hi Peter, I have to remember already ;-) - Just uninstall did not solve - So, I deleted program directory additionally, and hmmm maybe xul.mfl in profile
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.