Closed Bug 61861 Opened 25 years ago Closed 25 years ago

Huge amounts of disk space wasted by Chrome directory

Categories

(SeaMonkey :: General, defect, P3)

x86
Windows 95
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 53462

People

(Reporter: graham.knap, Assigned: asa)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win95; en-US; m18) Gecko/20001130 BuildID: 2000113004 The Chrome directory isn't actually all that huge, but it wastes tons of disk space due to the huge number of tiny files -- especially on a dumb filesystem like FAT. On a 2gig FAT16 drive with 32k clusters, this is what I see: 7,956,577 total bytes in 2,690 files 90,963,968 bytes disk space occupied, 91% slack You could solve this problem by concatenating groups of files together... Reproducible: Always Steps to Reproduce: I collected this statistic using Norton Utilities 8.0's "File Size" utility -- but you should be able to see it just by unzipping mozilla and watching your disk space drain away...
If you download the installer version of Mozilla you'll see that there's not so many files. All the resource files were put in jar files (basically zip files) a while ago. The .zip version of mozilla nightlies have still both the jar and the resource files included, so this is IMHO an INVALID bug. Feel free to object if you think that's not correct.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
Well, since you can easily re-generate the flat chrome by simply unzipping the jars (roughly), it is not necessary to have them in the zip packages. I think this bug is not really invalid, but more a duplicate of bug 59110 (which is a duplicate of bug 53462). In any case, this is a known problem.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 53462 ***
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
vrfy dupe
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.