Closed
Bug 674514
Opened 14 years ago
Closed 14 years ago
Profile Directories get way to large since FF4 due to the Chunk Size set in some Sqlite Files.
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 666611
People
(Reporter: plattner, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110422 Ubuntu/10.04 (lucid) Firefox/3.6.17
Build ID: 20110422054454
Steps to reproduce:
Upgraded from Firefox 3.6.1.6 to FF 4 and shortly after to FF 5 .
Actual results:
I realized that since FF 4 the places.sqlite has been given a chunk size of 10M, means it starts with 10M and grows in 10M steps.
Same Problem with the urlclassifier3.sqlite file(5 MB Chunk size)
Since we used Firefox to be delivered on our Systems, wich have limited Resources (say 512 MB Ram and max 1GB Flash Drive), this is very unpleasent for us.
The Partition on our Systems for Firefox Profiles is about 30M, so you can see that after 1-2 Profiles stored it's full.
When searching in Forums for solution for this behaviour, i also learned that companies wich provide their employees Firefox Profiles over the Network aren't happy with that too (regarding Network Traffic, say 100 Profiles with about 25M = 2500M !!). Same Problem if you have limited Disk Quota for Users.
Expected results:
I would like to see a preference , so that the Chunk Size can be set to a lower value (say 1K) or to deactivate this behaviour altogether.
When looking into the Function SetGrowthIncrement in the storage/src/mozStorageConnection.cpp Source file, i've seen that on Android System this behaviour is deactivated through a compile Flag. This make sense due to the limited Resources on Android System.
Since we have the same Problem, and many other Companies/People i would like to see a Preference in FF to deactivate the Setting of the Chunk Size for the Sqlite files.
Updated•14 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•