Closed Bug 391864 Opened 18 years ago Closed 18 years ago

Don't keep a disk cache of file: favicons

Categories

(Camino Graveyard :: General, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Camino1.6

People

(Reporter: stuart.morgan+bugzilla, Assigned: stuart.morgan+bugzilla)

Details

(Keywords: fixed1.8.1.8, Whiteboard: [camino-1.5.2])

Attachments

(2 files, 1 obsolete file)

Attached patch fix (obsolete) — Splinter Review
While having an in-memory cache of file: and about: favicons makes sense, persisting them to disk doesn't.
Attachment #276299 - Flags: superreview?(mark)
Comment on attachment 276299 [details] [diff] [review] fix Looks like IconCache.plist is written with entries that ought to be memory-only. This is a problem in the existing SiteIconCache.mm. This code can use [inURIAsNSURL scheme], or even [inURIAsNSURL isFileURL]. Gecko's case-insensitive about schemes, can we be too?
Attached patch v2Splinter Review
Uses isFileURL. I removed the about: part, since looking at my machines here I appear to have been mistaken that about: has favicons show up. I'm not sure what you mean about memory-only things being written to disk; this patch prevented file: urls from being added in my testing, and I don't see a code path where memory-only objects can make it to disk. Existing file: entries will certainly still be there after this patch, but since cleaning old stuff out is a general problem that we still really need to solve I don't want to make a hacky solution just for file: URLs.
Attachment #276299 - Attachment is obsolete: true
Attachment #276492 - Flags: superreview?(mark)
Attachment #276299 - Flags: superreview?(mark)
Comment on attachment 276492 [details] [diff] [review] v2 ([]) unnecessary here. This method now calls [inURIAsNSURL isFileURL] twice - please reduce to a single call. sr=me with those changes.
Attachment #276492 - Flags: superreview?(mark) → superreview+
Landed on trunk and MOZILLA_1_8_BRANCH with requested changes.
Status: NEW → RESOLVED
Closed: 18 years ago
Keywords: fixed1.8.1.7
Resolution: --- → FIXED
Summary: Don't keep a disk cache of local (file:, about:) favicons → Don't keep a disk cache of file: favicons
Nominating for 1.5.2.
Flags: camino1.5.2?
Any reason not to land this on 1_5 for 1.5.2?
No real reason not to, so I'd be fine with it, but I don't see any compelling reason to do so either, and we usually don't toss random changes into minor update releases.
Is this not enough of a help against the ever-expanding site icon cache?
I think it's a well-contained fix for part of a very bad larger problem. It'll help some, though maybe not tons, but since it's simple/contained, I think we should land it.
Flags: camino1.5.2? → camino1.5.2+
Since there wasn't a final diff of the trunk/18branch patch, I'll attach the diff I made for landing this on the 1_5 branch.
Landed on the CAMINO_1_5_BRANCH for 1.5.2.
Whiteboard: [camino-1.5.2]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: