Comment 3 for bug 234661

> 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.