Closed Bug 268773 Opened 20 years ago Closed 19 years ago

Illegal Instruction Exception in Firefox 1.0 with Windows Server 2003

Categories

(Firefox :: General, defect)

x86
Windows Server 2003
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: nowandever29, Assigned: bugzilla)

Details

Attachments

(2 files)

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; .NET CLR 1.1.4322)
Build Identifier: http://www.mozilla.org/products/firefox/

When starting Firefox on Windows Server 2003 with all current patches as of 
11/09/04, I get Illegal Instruction Exception (0xC000001D) in firefox.exe at 
location 0x004B36D8.  

Reproducible: Always
Steps to Reproduce:
1. Install firefox, do not reboot
2. Start firefox
3.

Actual Results:  
When starting Firefox on Windows Server 2003 with all current patches as of 
11/09/04, I get Illegal Instruction Exception (0xC000001D) in firefox.exe at 
location 0x004B36D8.  

Expected Results:  
Start

When starting Firefox on Windows Server 2003 with all current patches as of 
11/09/04, I get Illegal Instruction Exception (0xC000001D) in firefox.exe at 
location 0x004B36D8.
OS:Window Server 2003 patched as of 09/11/2004
Program:Mozilla FIrefox 1.0
If launched under admninistrator user, it starts normally, if started under any
other user, it fails to start, often trying repeatedly to fork itself.
Performed several installations, also with pre-cleaning of the profile and
talkack folder.Brief log 1 of event error attached, brief log 2 will follow.
OS:Window Server 2003 patched as of 09/11/2004
Program:Mozilla Firefox 1.0
If launched under admninistrator user, it starts normally, if started under any
other user, it fails to start, often trying repeatedly to fork itself.
Performed several installations, also with pre-cleaning of the profile and
talkback folders.Brief log #2 of event error attached,integrates previous
attachment.
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: