Closed Bug 74301 Opened 24 years ago Closed 21 years ago

New cache not properly updating object size

Categories

(Core :: Networking: Cache, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla0.9.1

People

(Reporter: tenthumbs, Assigned: gordon)

References

Details

(Whiteboard: [cache])

Attachments

(2 files)

With an 0331 nightly build, the new cache appears not to update the size of an object on reload. I have an SSI HTML page which changes size constantly. The cached file appears to be the largest size ever seen so Mozilla display garbage eventually. Attached is a copy of the cached object. Note the multiple </HTML> tags. Everything after the first one is junk but mozilla displays the junk.
tenthumbs@cybernex.net, did you forget to attach the cached copy?
I'm guessing mozilla is not truncating the disk file properly.
Whiteboard: [cache]
Target Milestone: --- → mozilla0.9
Please verify this with today's landing.
It's still there with an 0407 nightly trunk build. One interesting thing is that about:cache reports bogus size values for objects that chage a lot. In my case, the largest test page was 1571 bytes but, after about 25 reloads, about:cache said the page was 17258 bytes.
Target Milestone: mozilla0.9 → mozilla0.9.1
Hmm...we can't get there from here. In nsCacheEntryDescriptor.cpp, the nsOutputStreamWrapper::OnWrite(PRUint32 count) method has no inkling of the offset being written to, so it keeps adding the count to the end. Obviously a major malfunction...
Fix checked in. There is still a bug in that nsFileTransports won't truncate files properly, but we'll handle that as a separate bug.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Is there a bug# for the nsFileTransports bug?
*** Bug 86469 has been marked as a duplicate of this bug. ***
I just created bug 86474 to track the lack of truncation with nsFileTransports, but the problem may be fixed for the cache by other means.
Do these symptoms still appear? That is, is getting bug 86474 fixed necessary to prevent garbage appearing?
*** Bug 91254 has been marked as a duplicate of this bug. ***
Still there in an 07-18-21 Linux nightly but the behavior is somewhat different. You now have to load a dynamic page, go off to some other pages, and then return with the Back button. Yes, it's still a truncate problem. The garbage seen is really there in the disk cache.
Status: RESOLVED → VERIFIED
QA Contact: tever → cacheqa
sorry, wrong bug. jetlaggged comment.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Ben, you're causing me extra work when you mess with dead bugs like this.
Status: REOPENED → RESOLVED
Closed: 23 years ago21 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: