New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blank file when saving with full hard drive #2923

Closed
oolong opened this Issue Nov 2, 2014 · 5 comments

Comments

Projects
None yet
4 participants
@oolong

oolong commented Nov 2, 2014

I just opened a sketch I've been working on in Processing 2.1.1 in Processing 3, only to find that the main file was totally blank. Looking with a file manager, the file is only 1 byte big. It's still blank when I open it in Processing 2.1.1, so maybe the Processing 3 thing is a red herring.

The other files of this sketch seem to be fine. I'm really pretty certain I didn't blank this file myself before I closed it and re-opened it.

edit: My hard drive is full, and I hadn't realised, so this is at least partly my fault - but shouldn't Processing say 'failed to save!!' if it fails to save, or something like that?

edit 2: I cleared a load of space on my hard drive, but maybe I didn't save it properly afterwards - it's truncated the file this time, rather than completely failing to save. This time I selected all and copied it to my clipboard before saving, in case something like this happened again, but apparently Processing also quietly empties the clipboard when you quit, or something?

@oolong oolong changed the title from Blank file on opening work in Processing 3 to Blank file when hard drive full (in Ubuntu) Nov 2, 2014

@PauloBarbeiro

This comment has been minimized.

Show comment
Hide comment
@PauloBarbeiro

PauloBarbeiro Dec 4, 2014

I am facing the same problem.

PauloBarbeiro commented Dec 4, 2014

I am facing the same problem.

@benfry benfry changed the title from Blank file when hard drive full (in Ubuntu) to Blank file when saving with full hard drive Jan 16, 2015

@Pomax

This comment has been minimized.

Show comment
Hide comment
@Pomax

Pomax Jan 17, 2015

ran into this as well - effectively lost a day's work because it didn't report an error

Pomax commented Jan 17, 2015

ran into this as well - effectively lost a day's work because it didn't report an error

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jan 19, 2015

Member

Contributions welcome. Obviously anything that saves a file is code that needs to be rewritten very carefully. It's been on my list (to use proper practice and save temp files first), but I've never had the time to implement it.

Member

benfry commented Jan 19, 2015

Contributions welcome. Obviously anything that saves a file is code that needs to be rewritten very carefully. It's been on my list (to use proper practice and save temp files first), but I've never had the time to implement it.

@Pomax

This comment has been minimized.

Show comment
Hide comment
@Pomax

Pomax Jan 19, 2015

Unfortunately I'm involved in too many projects already and won't have time to help dive into this for probably a considerable amount of time. Happy to report, unable to do much more than that =/

Pomax commented Jan 19, 2015

Unfortunately I'm involved in too many projects already and won't have time to help dive into this for probably a considerable amount of time. Happy to report, unable to do much more than that =/

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Jan 21, 2015

Member

Turns out this was mostly done in the alpha releases, but I've added more bulletproofing to hopefully avoid the situation for 3.0a6.

Member

benfry commented Jan 21, 2015

Turns out this was mostly done in the alpha releases, but I've added more bulletproofing to hopefully avoid the situation for 3.0a6.

@benfry benfry closed this Jan 21, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment