This project is read-only.
1

Resolved

TEMP area disk clean up policy needed

description

Some of these larger conferences can generate GB's worth of files in the TEMP area (jpeg renderings mostly). Currently nothing is done to clean that up...

comments

gwatts wrote Jun 15, 2008 at 12:46 PM

Perhaps have a button on the last page of the app that says "clean up temp files" and also close. Then the user could choose. Have some sort of help to explain why?

wrote Jun 15, 2008 at 12:47 PM

wrote Jun 15, 2008 at 12:51 PM

wrote Jan 9, 2010 at 5:12 AM

wrote Jan 9, 2010 at 5:15 AM

wrote Feb 23, 2010 at 12:47 PM

gwatts wrote Feb 28, 2010 at 8:41 PM

All jpg and other rendered files should get cleaned up after a rendering, right? Any reason at all not to?

gwatts wrote Feb 28, 2010 at 8:41 PM

The first thing to do is figure out where all the temp files come from! And then work from there.

gwatts wrote Mar 13, 2010 at 11:15 PM

Judging from workflow: there is no need for any temp files to hang around ever. The ones that are there when a crash happens are useless as the code currently has to re-run things (incase there was an update, etc.).

gwatts wrote Mar 14, 2010 at 1:12 AM

Fixed up the URI fetecher...

gwatts wrote Mar 14, 2010 at 6:42 AM

Actually, stuff was distributed all over the place - so there was quite a bit of small things that had to be cleaned up and coordinated in order to make this work correctly.

wrote Mar 14, 2010 at 7:11 AM

wrote Feb 2, 2013 at 4:05 AM

wrote May 16, 2013 at 12:27 AM

wrote May 16, 2013 at 12:27 AM

wrote Jun 12, 2013 at 1:42 AM