Closed Bug 268728 Opened 21 years ago Closed 20 years ago

Immediate crash when trying to access network drive paths

Categories

(Firefox :: File Handling, defect)

x86
Windows Server 2003
defect
Not set
critical

Tracking

()

RESOLVED EXPIRED

People

(Reporter: wbayer, Assigned: bugs)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Selecting File, Open File, Look in displays a list of network drives. Selecting anything other than the C: drive results in an immediate crash of Mozilla Firefox 1.0. I disabled the Spellbound 0.60 extension in case this was contributing. Reproducible: Always Steps to Reproduce: 1. Selecting File, Open File, Look in 2. Choose any shared network drive 3. Instant death. Actual Results: the browser crashes instantly, withour even a talkback report. Expected Results: Dispayed the folders on the network drive.
Correction, not all shared network drives trigger this Firefox 1.0 crash. Some shared drives do exhibit the expected behaviour and display their folders in the "Open File" window. It is not immediately apparent why some shared drives consistently cause this crash, while others behave normally. This is definitely not a file permissions issue as Windows explorer and other applications display and allow write access to the same shared drives causing Firefox 1.0 to crash.
This can be repeated and it happens when you try to import a security certificate to trust a root certification authority. Steps to repeat this for importing a certificate: 1.) Go to Options. 2.) Go to advanced settings. 3.) Go to manage root certificates. 4.) Go to the root CA certificates tab and click import. 5.) Then go to "My Network" 6.) Click on "View entire network" 7.) Click on "Microsoft Windows Network" 8.) Click on the domain/workgroup of your network where the computer with the security certificate is part of. 9.) Click on the computer that has the network share of the security certificate. 10.) Access the network share and try to open the file which has the security certificate. Firefox crashes and talkback is given. Expected Result: Open the CA certificate file and present a prompt to specify trust of certificate. Actual Result: Firefox crashes. I am currently running Windows 2003 Enterprise Edition. This occurs whether I am running as restricted user or administrator. Mozilla/5.0 (Windows; U; Windows NT 5.2; ja-JP; rv:1.7.5) Gecko/20041108 Firefox/1.0
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: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.