User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:184.108.40.206) Gecko/20070725 Firefox/220.127.116.11 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:18.104.22.168) Gecko/20070725 Firefox/22.214.171.124 Is it a bug or a peeve? Either way I am not using Firefox much anymore because I have to restart my computer to get rid of the parent.lock file before I can open FireFox 2.0 in Vista. This is an unacceptable inconvenience that has driven me back to IE. I hope you can get this fixed soon. Yes, I read everything on the support page, scanned for the trojans (poison, etc,) with four (4!) different programs, and searched online for a fix. I now have a desktop shortcut to the parent.lock file because if I do not delete it before I open Firefox then I get a message saying it is in use. When I try to end the 2K firefox.exe process in the task manager it just says "Access Denied". Let me know when you get this fixed. Sometimes I can open another Firefox window but the smaller 2K process is always running in the background and it cannot be shut down. I am sure that there are a lot of former users of Firefox who are reluctantly returning to IE, which opens promptly every time with no delays. Thanks, R Bond Reproducible: Always Steps to Reproduce: 1.Just try to start Firefox in Vista. It always jams after 2 or 3 starts. 2. 3. Actual Results: simple as above
Have you tried: - Firefox's safe-mode to exclude extension/theme problems - a new profile - a reinstall in a new empty folder? http://kb.mozillazine.org/Safe_Mode_(Firefox) http://kb.mozillazine.org/Profile_Folder
"Access Denied" usually means that Firefox can't be ended because it's hangs somewhere in kernel Mode. Do you use a third-Party Firewall or somethinng that is using a kernel mode driver which could cause that ?
Sounds like a duplicate of Bug 395524.
=> incomplete - can't tell, reporter has abandoned ship but feel free to comment
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.