Bug 967 : when your disk is full, Processing zeroes files when it tries to save changes
Last modified: 2009-10-18 10:16



Assigned To:

Attachment Type Created Size Actions

Description:   Opened: 2008-10-19 23:43
A friend of mine reported this at
http://twitter.com/mikekuniavsky/statuses/963127752 and I wanted to make
sure it went a bit further than that!

Apologies if this is hard to reproduce or if it has already been fixed, I
haven't had a chance to check it yet on my machine.
Additional Comment #1 From fry 2008-10-20 05:48
Hm, this is tricky. Lots of software has the same problem--OS X even nuked
my user account (all my prefs zeroed out) once when my disk got below 250 MB.

And unfortunately we can only check the amount of free disk space starting
in Java 6. Which means using reflection to get the API, and no Mac OS X
except for a tiny portion of people:

Thanks for reporting this--it's frustrating to have complaints aired that
never make it to me! I'll see what I can do.
Additional Comment #2 From fry 2008-10-20 05:55
that said, what we actually need to do is write temp files as we're saving,
and only replace and rename the old file once the initial file has
successfully saved, which is the bigger problem. it's been on the todo list
but now i've filed an actual item for it as bug #968.
Additional Comment #3 From TomC 2008-10-20 08:48
Great to hear, thanks Ben!

FWIW I periodically check Twitter for this sort of thing, as well as
del.icio.us and Processing Blogs of course. This is the first one I've seen :)
Additional Comment #4 From fry 2009-10-18 10:16
now fixed for 1.0.8. sorry to not get at this sooner, somehow it fell off
the radar. thanks again for the report.