210003 - possible cache management problem

Status: VERIFIED DUPLICATE of bug 198806

(Core :: Networking: Cache, defect)

Description

[Dirk Munk]

User-Agent:       Mozilla/5.0 (X11; U; OpenVMS AlphaServer_DS10_466_MHz; en-US; rv:1.4) Gecko/20030528
Build Identifier: Mozilla/5.0 (X11; U; OpenVMS AlphaServer_DS10_466_MHz; en-US; rv:1.4) Gecko/20030528

I've noticed the following problem that seems to be a cache management error:

1. I download several images in several browser tabs
2. I right-click on the images to save them to disk
3. I get an error popup with the following message:
"The link could not be saved. The web page might have been removed or had its
name changed."
4. to solve the problem, I clear the cache (from preferences).
5. I reload the images
6. Now I can save them to disk.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.

Comment 1

[Dirk Munk]

Sorry, Reproducible should be: sometimes

Comment 2

[Matthias Versen [:Matti]]

Do you use Netscape7.x with the same profile ?

Comment 3

[Colin Blake]

> Do you use Netscape7.x with the same profile ?

No, he doesn't. Because there is no Netscape 7 on OpenVMS :-)

Comment 4

[Dirk Munk]

On Windows 98SE I use Netscape 7.02. However in Windows I can set the memory
cache, on VMS I can't. Only the disk cache can be set. The rest of the settings
is quite similar

I haven't seen the problem with Netscape (so far).

Comment 5

[Colin Blake]

Any pattern to the images you can't save? For example, are they all from the
same site?

Do you use a proxy server?

Please try to find a case you can reproduce.

Comment 6

[Dirk Munk]

No, I do not use a proxy server.

I've seen it with several web sites. Now I'm thinking about it, it may happen
when I download many (big) images at once. 

Right-click image 1, image 2, image 3 and so on, to load them in different tabs.

I'm just wondering what 'clear cache' does, it will not cleanup the disk cache!!
I just noticed that all files in the disk cache are > 2 months old ?!?!

Puzzling ......

Comment 7

[Colin Blake]

"clear disk cache" should delete all the files. If its not, then I would suspect
that the files which are left are ones from when Mozilla has crashed and its
"lost track" of them. So long as Mozilla is not running its OK to just delete
the entire cache directory. It will get recreated automatically next time you
run Mozilla.

By the way, you know about "about:cache", right?

Comment 8

[Dirk Munk]

Yes, I know the "about:cache" command.

I've used it before, and now I can see my disk cache already was corrupted at
that time.

About:cache should give Memory cache statistiscs and Disk cache statistics. I
had never seen anything else as Memory cache statistics, but after deleting all
cache files I know have Disk cache statistics as well !

Some observations:

The Memory cache statistics mention a Maximum storage size of 20MB, and Storage
in use (at the moment) of 50MB (!!). I can imagine that this discrepancy causes
addressing problems. I suppose the Storage size is dependent of my account
settings in Authorize ?

Mozilla does not give a warning if the disk cache is corrupt, and will happily
start. In my view that is wrong, it should give a warning.

There is also a cache_trash directory with a lot of sub directories. I cleared
that directory as well. 

Comment 9

[Colin Blake]

I have entered bug 210481 to track the work required to correctly size the
memory cache for OpenVMS. 

Are you able to save images now that the disk cache has been cleaned up?

Comment 10

[Dirk Munk]

It hasn't happened so far, but I will keep trying to see what happens.

I also tried to find a correlation between the memory cache sizes and WSmax,
WSextent and PGFLQUO. I could not find one on first sight.

However I do remember trying to load as many pages as possible, and I got to
169MB memory cache in use (I was able to see that) before Mozilla crashed.
Since my WSextent is set to 400000 pagelets or 200MB, it almost seems as if
Mozilla crashed when it tried to break the 400000 pagelet barrier.

At that time my disk cache was corrupted !

Comment 11

[Dirk Munk]

After reading the whole thread of bug 198806, I'm sure this is a duplicate of
that bug. All the problems are there, incl. saving images.

*** This bug has been marked as a duplicate of 198806 ***

Comment 12

[benc]

V/dupe.