Closed Bug 266595 Opened 20 years ago Closed 20 years ago

Cache is using a folder that can potentially cause long load times for roaming profiles

Categories

(Firefox :: Settings UI, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 74085

People

(Reporter: smcneice, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20041026 Firefox/1.0RC1 The Cache for all the versions of firefox I have used up to 1.0rc1 have used the 'application data' folder in windows nt/2000/xp/2003 profiles, if roaming profiles are being used this folder is included in the profile and could potentially have 50megs of data to move on each logon and logoff, this issue could turn away companies from using firefox, the best place to put the cache folder is under the 'local settings\application data' folder this is not carried with the profile, I really see no need for the cache to follow a profile, Reproducible: Always Steps to Reproduce: 1.Install Firefox 2.browse a few pages 3.see how large the cache folder gets rather quickly Actual Results: roaming profile took longer to load Expected Results: used the 'local settings\application data' folder There is a work around for this for windows where you can exclude folders under the 'application data' folder but this work around has limitations where it will only accept so many characters, and with so many other products using this same folder where they do not need to, it becomes a major issue,
Please search before filing new bugs. IMO duplicate of Bug 74085. Please resolve it.
*** This bug has been marked as a duplicate of 74085 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in before you can comment on or make changes to this bug.