Closed Bug 466975 Opened 16 years ago Closed 16 years ago

Two instances of Profile folder on Windows

Categories

(Firefox :: Settings UI, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: goegoeh, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4

Hey. I have a problem with Firefox constantly hanging on startup. I've been browsing all sorts of information on how to eliminate this problem but I've had no luck so far. One tip was to create a new Profile, which I did. This solves the problem for a short period, then the browser is back in business hanging for at least a minute on startup.
During this process of creating a new profile, I discovered that Firefox creates two sets of Mozilla folders on my harddrive. One is created in <code>C:/Documents and Settings/User/Application Data/Mozilla/Firefox/Profiles/</code>, and the other one is created in <code>C:/Documents and Settings/User/Local Settings/Application Data/Mozilla/Firefox/Profiles/</code>. Why does Firefox need two separate, but identical, Profile folders? Is there something strange going on with my system?

The bug is present regardless of plugins and themes used.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
I believe this is for the location of the cache. Do you really see a whole profile with bookmarks etc.?
Yes, one is used only for the cache and the directory is a local system directory and the other is a roaming directory with all the user data.
incomplete without more information
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
I have solved this problem and it is now a non-issue. The hang problem resides within Firefox' live bookmarks system. I have exported and removed all my bookmarks from Firefox and it has stopped hanging.
Resolution: INCOMPLETE → INVALID
You need to log in before you can comment on or make changes to this bug.