144253 - large tarball cached while being saved; disk full report on wrong partition

Status: RESOLVED DUPLICATE of bug 91795

(SeaMonkey :: General, defect)

Description

[Martins Krikis]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc2) Gecko/20020510
BuildID:    2001051009

These are non-critical bugs, possibly merely wishlist items.
There are a number of places for improvement here, the story follows.

My disk cache size is set to 50M, it is in my /home partition.
I was downloading a 68M tarball (.tar.gz), but there was not
enough space for it in /home, so I was saving it to /tmp, which
is in a different partition. While saving the tarball to /tmp
(using some temporary file name), Mozilla was also cacheing it
in Mozilla cache in my /home directory. 
  Wish/bug #1: why cache *.tar.gz? 
  Wish/bug #2: why cache something larger than space 
               devoted to cache? 
  Wish/bug #3: why cache something that is being saved to disk?
  Wish/bug #4: why cache something that is being saved to a 
               different partition than where cache is (double
               the work for the disk)?

When I ran out of space in /home partition (still plenty of space
in /tmp), mozilla popped up a dialog saying that there is not
enough space in /tmp.
  Bug #5: that was a lie---plenty of space in /tmp.

If I'm not mistaken there was a suggestion to free some space or
save elsewhere. I did free up space in /home, but it was too late---
I could not continue this save operation.
  Wish/bug #6: it would be nice to let the user click a "Continue"
               or "Ignore" button or something to repeat the check
               for space and continue saving if now possible.
  Wish/bug #7: or it would be nice to move the so far saved piece
               elsewhere without loosing anything and continue
               saving the rest there.

Upon repeating the save operation of the same tarball at the same
place I was offered to overwrite the incomplete previous save attemp.
  Wish/bug #8: perhaps in a case like this, Mozilla could offer to
               continue from the place where it bailed on previous
               attempt and not redo it from the beginning? Alright,
               this depends on server support, so we can forget about
               it. Would be nice, though.

After finishing the save operation, the extra copy in the cache
was immediately deleted.
  Wish/bug/question #9: why bother cacheing something that gets
                        thrown out as soon as it has been downloaded?

OK, so 1 bug, 8 wishes or questions. Maybe some of this can be
addressed sometime? Thanks.


Reproducible: Didn't try
Steps to Reproduce:
1.Pick a large tar.gz file to be downloaded. 
2.Make sure there isn't enough room for it in /home.
3.Save it to another partition, where there is room.

Actual Results:  out of space error given about the wrong partition, saving
aborted even though there was enough space to save it...

Expected Results:  not cached, not ran out of space where I wasn't saving it,
and happily saved where I had space. could have offered to
continue or move elsewhere after I've freed some space...

Comment 1

[gavin long]

You're seeing problems covered by bug 55690 and its (many) dependencies.

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

Comment 2

[Boris Zbarsky [:bzbarsky]]

Actaully, no.  Reporter is seeing a different bug, but the "writing huge files
to cache" bug just got fixed... (I can't find the bug# at the moment).

Comment 3

[gavin long]

Boris: I just had a fairly concerted hunt for the "writing huge files
to cache" bug, but I can't find it.  On re-reading bug 55690, I agree that it
may not be the best one to dupe this against, but several of the dependencies
are relevant.  

Having just read loads of 'em, there are quite a few bugs kicking around on this
whole topic, including a couple of flamewar^H^H^H debates.

Comment 4

[gavin long]

Aha.  I think Boris was referring to bug 91795, which is MUCH more relevant to
the description given above.  Re-opening to dupe properly, apologies for the
spam this will create.

Comment 5

[gavin long]

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

Comment 6

[Martins Krikis]

91795 seems to be about memory consumption, memory caches.
The bug 144253 was about needless caching to disk.
I don't think they have anything in common, but you may
know better, especially if both are fixed by the same
"new download manager" or something.