Open Bug 1435300 Opened 7 years ago Updated 3 years ago

about:cache does not show all entries in caches

Categories

(Core :: Networking: Cache, defect, P3)

defect

Tracking

()

People

(Reporter: long, Unassigned)

Details

(Whiteboard: [necko-triaged])

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.1 Build ID: 20171107205422 Steps to reproduce: Entered about:cache in my url bar then clicked "List Cache Entries" under either memory or disk. Actual results: It says there are 2351 entries in my disk cache but the page it produces only lists about 874 (I just grepped for "http"). Expected results: It should have displayed all 2351 entries.
At least I can see a similar discrepancy with unzipped installer of official en-US SeaMonkey 2.53a1 (NT 6.1; WOW64; rv:56.0) Gecko/20100101 Firefox/56.0 Build 20170706013410 (Default Classic Theme) on German WIN7 64bit: about:cache "Information about the Network Cache Storage Service" tells Number of entries: 12157 After copy/paste of page contents into a spreadsheet I see only 4246 table rows for entries. But who can know whether the problem is not in "Number of entries"? @Reporter: a) Why do you assume that list has too few entries and the problem is not a wrong value for "Number of entries"? b) Did you see correct number of entries with older SM versions?
Flags: needinfo?(long)
about:cache is all core. If it is real I doubt it is a SeaMonkey problem. Maybe you can recheck with a corresponding Firefox version.
Yeah, same thing happens in FF 58.0.1 and I have no idea which part is "incorrect" (the count vs. the actual entries displayed)
Component: General → Networking: Cache
Flags: needinfo?(long)
Product: SeaMonkey → Core
Version: SeaMonkey 2.49 Branch → unspecified
Assignee: nobody → michal.novotny
Priority: -- → P3
Whiteboard: [necko-triaged]
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true

Unassigning Michal to move bugs back to triage pool.

Assignee: michal.novotny → nobody
Status: ASSIGNED → NEW
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.