Closed Bug 211141 Opened 22 years ago Closed 21 years ago

Cannot start new version. Immediately issues illegal operation fault.

Categories

(SeaMonkey :: General, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: r.mariotti, Unassigned)

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3.1) Gecko/20030425 Build Identifier: www.mozilla.org Mozilla is great. I'm currently up to 1.31b and an anxious to upgrade to 1.4. Twice this month I downloaded the latest version (today is was finally referred to as version 1.4) and did the normal install. Upon completion the installation process "proc-checks" (i.e.: dies with an "invalid operation"). I tried to capture the message detail section without any luck. But in order to report this bug I had to reinstall the previous version 1.31b. I searched your bug lists and did not find anything that seems to relate to this. So that's why this message. Thank you. Reproducible: Always Steps to Reproduce: 1. Doulble click on the Mozilla ICON. 2. 3. Actual Results: halts with the infamous gray illegal operation dialog box. Expected Results: Worked? as before?
doesn't block development.. Reporter: Please uninstall Mozilla, delete the whole Mozilla application folder manully and reinstall Mozilla. You will not loose your Mozilla profile with this steps..
Severity: blocker → critical
Keywords: crash
i am getting the same thing. here is some info: AppName: mozilla.exe AppVer: 1.4.20030.62408 ModName: xpcom.dll ModVer: 1.4.20030.62408 Offset: 00040769
Happens to me too. Tried several RC, including today's release (June 30). Tried windows (98se) uninstall for 1.3.1, then install of 1.4-at launch attempt immediately got gray box also. Same result from double click and quicklaunch....
Happens to me too. I first tried to update from 1.3 final to 1.4rc1 and got the crash. Reinstalling 1.3 final worked but it was complaning about a missing dll (xpcom_compat.dll). With 1.4 final, I'm trying again and I get the same crash. I tried removing the old 1.3, wiped out the program files folder and the profile (made a backup of course), but still happens. System: WinXP (dual P3@500, 512 MB, 120 GB but I guess that's irrelevant here). XP crash dialog info: AppName: mozilla.exe AppVer: 1.4.20030.62408 ModName: xpcom.dll ModVer: 1.4.20030.62408 Offset: 00040769 Note 1: I get the _exact_ same behavior on my laptop (Win2k, latest SP, etc.). Note 2: Firebird 0.6 works perfectly right out of the box. Note 3: I believe this is a dup of bug #211156 so I'll mirror my comment there too.
Note: since I believe this is a dup of bug #211156, I'm "cross-posting" my comment here too. I finally managed to have 1.4 final working. What I did was: - remove the broken 1.4 (crashing at startup in xpcom.dll) - thoroughly find all "*mozilla*" files or folders on my drive. Nothing significant found there. The c:\program files\mozilla.org\Mozilla was still there so I simply eradicated it. - thoroughly scanned the registry for "mozilla" items. - Removed HCKU\Software\Mozilla (was there but empty) - Removed HKLM\FullCircle\TalkBack - Removed HKLM\SOFTWARE\Classes\MozillaXXX where XXX=GIF, HTML, JPEG, MNG, PNG, XHTML, XML, XUL. - Removed HKLM\SOFTWARE\Classes\mozMapi Then: - installed the NetInstaller for 1.4 final. Mozilla worked just fine :-) - removed netinstalled version and tried again with full 1.4 installer. Works fine now. My assumption is that the problem resides in the registry and the OS is irrelevant (i.e. 98/2k/XP exhibit the same problem). Hope this help.
I don't think that mozilla crashes because of registry entrys. It could be the GRE directory under c:\dokuments and settings\.. (not the profile)
Please uninstall all mozilla versions you have, delete any mozilla.org directory under program files, delete any mozilla directory in unser common files and then install Mozilla 1.6. Reopen if you still experience the same crash.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.