firefox crashes without messages when disk full

Bug #406237 reported by Francesco Potortì
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
firefox (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: firefox

Firefox crashed on me without any warnings or messages because the disk was full. This happened shortly after I had opened a new tab. This is Firefox 3.0.11+build2+nobinonly-0ubuntu0.8.10.1 on Ubuntu 8.10.

It was not easy to diagnose the reason for the crash, as launching Firefox again produced a window missing some of the decorations and with empty bookmark menus, but still no error messages, either in pop up window or on the command line. Same if called with -safe-mode. When in this situation, it crashed as soon as the Tools / Add-ons or the Tools /Downloads menus were selected, again without any sort of messages. This behaviour persisted even after upgrading to
3.0.12+build1+nobinonly-0ubuntu0.8.10.1.

Revision history for this message
Adam Niedling (krychek) wrote :

I think this is not a Firefox-only issue. The user should be warned when disk space is low.

Revision history for this message
Francesco Potortì (pot) wrote : Re: [Bug 406237] Re: firefox crashes without messages when disk full

>I think this is not a Firefox-only issue. The user should be warned when
>disk space is low.

What you mention is a different problem, that is, the system should
monitor disk space usage and warn the user when it approaches zero.

However, what I am reporting is a bug in Firefox: when a program
encounters an error, it should not die without explanation, but should
signal an error. Firefox did not signal an error whan it died, and did
not signal an error whan, just after being restarted, could not display
all its widgets because of no disk space. This is a bug in Firefox, as
far as I can tell.

Revision history for this message
drew212 (mstngdrew212) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.
There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 406237, and any other logs that are relevant for this particular issue.

drew212 (mstngdrew212)
Changed in firefox (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for firefox (Ubuntu) because there has been no activity for 60 days.]

Changed in firefox (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.