Closed
Bug 394595
Opened 17 years ago
Closed 17 years ago
1.1.4 for OS/2 crashes in XPCOMCOR
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: ok34, Unassigned)
Details
User-Agent: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.8.1.4) Gecko/20070530 eSeaMonkey/1.1.2
Build Identifier: Seamonkey 1.1.4
(Notice: The build identifier that Bugzillas autofeatures inserts could not be used, for reasons below. Exact build identifier is unknown, build was downloaded 9/1, 10 pm).
Maybe this has been filed somewhere else, but it's hard to search for keywords XPCOMCOR and/or crash. I haven't found any notices on the newgroup, though.
After installing 1.1.4 (using the installer.exe over a functional 1.1.2) Seamonkey crashes each and every time during startup. There is no error message displayed, actually nothing gets displayed - not even the splash screen. In POPUPLOG I find this:
09-02-2007 00:15:54 SYS2070 PID 0048 TID 0001 Slot 008a
D:\BIN\SEAMONKEY\SEAMONKEY.EXE
RWSOS2->XPCOMCOR.32
182
I tried to start Seamonkey after deleting every single Plugin, but this did not help.
Reproducible: Always
Steps to Reproduce:
1.Install SM 1.1.4
2.Start it
3.
Actual Results:
Crashes silently.
Expected Results:
Startup.
Reporter | ||
Comment 1•17 years ago
|
||
I just realized that I did not try to install (regular) 1.1.4 over a regular build of 1.1.2, but over Peter Weilbacher's enhanced version of 1.1.2. So this bug may not be valid (I currently do not have to time to re-test this), therefore I mark this bug INVALID myself. Sorry for the confusion.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•