firefox crashed, when downloading an file on full hd

In Most cases where these data losses occur it will be due to the Disk Cache
saving enough data during a session to bump the disk up to the full point, or to
the user downloading enough files to use remaining space.

The shut down routine should check for disk sapce and if it is full the disk
cache should be emptied to free up some space. This is also a data loss, but
cache loss is far less severe than losing bookmarks, passwords, etc. Emptying
the cache should prevent loss of critical data in most cases, the exception
being people who have set their disk cache to zero size.

> Emptying the cache should prevent loss of critical data in most cases,
> the exception being people who have set their disk cache to zero size.

Or people who have the cache and profile on a different disks (or partitions).

> Or people who have the cache and profile on a different disks (or partitions).

True, but the real cause of these bugs is poor management of disk resources on
the part of the user, and someone who has gone to the effort to set up Mozilla
profiles on seperate disks/partitions is unlikely to ignore disk management
after that.

There is a limit on what can be done to save a user from himself. A Warning of
low resources at startup will help, but if that warning is set at resources less
than 100 MB downloading a large file and expanding the disk cache by surfing
sites can trigger this problem with no warning. There will also be people who
ignore the warning. Dumping the cache if there are low resources at shutdown
will save most (NOT all) users from losing critical data and fit in with the
bandaid nature of this bug.

I'm only sugesting this approach for the 1.6 release. A Better fix for these
related bugs needs to be found before 1.7 is released.

Clearing the cache at shutdown doesn't work. Or not in itself.
For example, the cookperm.txt is written when there are changes. This means that
it isn't written at shutdown. So, if the last attempt to wirte failed due to no
disk space, and then at shutdown there suddenly is disk space, the file is still
not written to disk.
Afaik, the same goes for cookies. I don't know about others.

What aren't we putting up a message immediately with something like cookperm.txt?

"Unable to write cookperm.txt because the disk is full. Please free some place
and then click OK"

would have been a nice one to get, but it looks like no one is biting to do this
work. getting too late for 1.6. moving to 1.7

I still think its a good idea to warn users when we get near the danger zone at
startup... doesn't need a lot of precision or lots of anticipation of what the
user might be loading into the disk cache for the upcoming session...

that said we would still need to get someone one to whip up a patch...

need to minus for 1.7a since no patch has appeared

Is bug 236153 a duplicate

Ben

*** Bug 239790 has been marked as a duplicate of this bug. ***

(In reply to comment #8)
> Is bug 236153 a duplicate
>
> Ben

No. That bug covers not being able to use Mozilla/Firefox at all because it
can't create a lock file. This bug covers
Mozilla/Firefox/<insert_gecko_browser_here> crashing because it can't write to
the cache file, therefore causing dataloss.

Neil, any chance you can help us out with something here?

*** Bug 240891 has been marked as a duplicate of this bug. ***

*** Bug 283891 has been marked as a duplicate of this bug. ***

Can you provide instructions as to how I can recover my saved email and news
preferences, and my saved email, after I have encountered the full disk problem?

I NEED to get back my record of saved email. I'm sure it's still sitting in
Mozilla's email database somewhere, but I don't know how to access it.

Michael, not only is there no work being done on this bug at the moment
(or at least none being recorded), but there been no substantive comment added to
it since December 2003.

You would be better off checking the FAQ and other troubleshooting resources
for the program that you are using (Thunderbird/MAS).

It seems that this bug is related to the Core product, isn't it ?

removing late-l10n since this on longer seems to be in any product release blocking paths

No comment in more that 1½ years, resetting A+QA.
Moz 1.7 has come and gone, resetting Target.

*** Bug 312216 has been marked as a duplicate of this bug. ***