Clearing cache does not zero out the cache in use size number until closing / reopening preferences window

VERIFIED FIXED in seamonkey2.10

Status

SeaMonkey
Preferences
--
minor
VERIFIED FIXED
6 years ago
5 years ago

People

(Reporter: Michael Lueck, Assigned: ewong)

Tracking

Trunk
seamonkey2.10

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [good first bug][mentor=Phil.Chee][lang=JS])

Attachments

(1 attachment)

(Reporter)

Description

6 years ago
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20100101 Firefox/9.0.1
Build ID: 20111220165912

Steps to reproduce:

Edit \ Preferences \ Open Twisty for Advanced \ Cache \ click the button "Clear Cache"

Official Mozilla binary build: Mozilla/5.0 (X11; Linux x86_64; rv:9.0.1) Gecko/20111221 Firefox/9.0.1 SeaMonkey/2.6.1

Installed via UbuntuZilla


Actual results:

Current cache size number did not go to 0.

If the Preferences window is closed, going back to the same menu path, THEN the number is already 0 without pushing the "Clear Cache" button a second time.


Expected results:

Should have gone to 0 right away without needing to exit the window and reopen the window.
Confirmed.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86_64 → All
Whiteboard: [good first bug]
Version: SeaMonkey 2.6 Branch → Trunk

Comment 2

6 years ago
I think ClearDiskAndMemCache() should call updateActualCacheSize() at the end.
(In reply to Philip Chee from comment #2)
> I think ClearDiskAndMemCache() should call updateActualCacheSize() at the
> end.

mentor=you then? :-) Or if it's really that easy, could fix it right away.

Updated

6 years ago
Whiteboard: [good first bug] → [good first bug][mentor=Phil.Chee][lang=JS]
(Assignee)

Comment 4

6 years ago
Created attachment 601881 [details] [diff] [review]
Zero out the cache in use size when clearing cache.
Assignee: nobody → ewong
Status: NEW → ASSIGNED
Attachment #601881 - Flags: review?(iann_bugzilla)

Updated

6 years ago
Attachment #601881 - Flags: review?(iann_bugzilla) → review+
(Assignee)

Comment 5

6 years ago
Pushed to comm-central:
http://hg.mozilla.org/comm-central/rev/4a8aad19f735
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Reporter)

Comment 6

5 years ago
I see this bug report has been flagged at a status of Resolved / Fixed. Now I am running the official binaries from Mozilla of: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120429 Firefox/12.0 SeaMonkey/2.9.1  and still see this bug present. Which version will finally include this fix?
(In reply to Michael Lueck from comment #6)
> Which version will finally include this fix?

2.10. It's always the version from Target Milestone (or lowest with "fixed" from Tracking Flags, if present). Unfortunately, some contributors forget to set the flags accordingly. I did this now for this bug (checkin to trunk was on 03-05 which is before 03-13 which was the date when 2.10 moved from trunk to Aurora).
Target Milestone: --- → seamonkey2.10
(Reporter)

Comment 8

5 years ago
Fix confirmed in Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10 Thank you! :-)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.