Open Bug 1107044 Opened 10 years ago Updated 2 years ago

Firefox ESR 31.2.0 "print to file" produces 0 length files when /tmp full


(Core :: Printing: Output, defect)

31 Branch





(Reporter: tero.t.nieminen, Unassigned)


User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Firefox/31.0
Build ID: 20141013035207

Steps to reproduce:

I printed some PDF files of web pages with print to file in Firefox ESR 31.2.0 (under RHEL 6.6 Workstation (64-bit)). It seemed to have gone as many times before without any problems.

Actual results:

I later noticed that the files produced were all 0 length even though Firefox had given  no warning or error message what so ever. With a little bit inspection I found out that I had earlier accidentally filled (or almost filled) my /tmp that seems to have gone unnoticed by Firefox.

Expected results:

Firefox ought to have given at least a warning that the files could not be created normally (and possibly a /tmp full hint).

Disk full condition (or quota full etc.) should never go unnoticed. It is quite possible that print to file is not the only operation potentially affected by this omission (printing might have failed also - though I didn't confirm that myself as /tmp full eventually caused other problems that needed to be resolved (ie. /tmp cleaned).
Component: Untriaged → Printing: Output
Product: Firefox → Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.