Closed
Bug 179655
Opened 22 years ago
Closed 22 years ago
cache not working efficiently ?
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: pml, Assigned: bugzilla)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826
When opening a page in phoenix with a lot of images, following a link, then
clicking 'back' to get back the the high image-density page seems to indicate
that the cache isn't being used effectively. The images always seem to load
again, very slowly. See lots of time waiting for page to re-populate.
This, of course, doesnt sound like a phoenix bug - but rather existing in the
moz codebase. Thing is that mozilla (M1.1) has no problem in this area.
Returning to a high image-density page sees them loaded instantaneously - no
latency at all indicating that the cache is working fine.
Problem only exists in phoenix.
Reproducible: Always
Steps to Reproduce:
1.Open high image-density page
2. follow a link forwards
3. click 'back' to return to page
4. images appear to be loaded from scratch again.
Comment 1•22 years ago
|
||
Reporter, you're using a 2.5 months old build. Things have changed a lot since then.
Personally, with 20021111, I don't see any of the problems you mentionned.
Please, update to a newer build (with a new profile) and reopen this bug if you
still see the problem. Verify that your disk cache is not empty as well (the
default setting should work fine).
Resolving as WORKSFORME
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 2•22 years ago
|
||
Marc:
uh, I'm reporting the bug using M1.1 which is 4 months old. The bug report is
about Phoenix, not 1.1
My phoenix agent is:
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021029 Phoenix/0.4
(Sorry, this was omitted from the bug report)
Installation was installed with a new profile.
You need to log in
before you can comment on or make changes to this bug.
Description
•