Well yes, that's why it's called a "cache", it holds your work temporarily until you either flush it or write/commit it permanently. In case of a premature reboot it's normal to lose your work.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This has also happened to me without system crashes etc. That is the file edits that have been made have not been committed to disk. Currently I am trying to flush cache manually often to prevent this. Part of the issue might be that I am working with a slow media.
Could the cache (or cache flushing) be made more aggressive (or disable it)? Or a setting to that effect? Currently I am left being unsure if my edits have been written down or not.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are using an external SDCard or portable hard drive, it's best to use the USB Icon in the Taskbar (lower right side of the taskbar) right click and "Eject" the disk. That will flush any chaching to the media.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well yes, that's why it's called a "cache", it holds your work temporarily until you either flush it or write/commit it permanently. In case of a premature reboot it's normal to lose your work.
This has also happened to me without system crashes etc. That is the file edits that have been made have not been committed to disk. Currently I am trying to flush cache manually often to prevent this. Part of the issue might be that I am working with a slow media.
Could the cache (or cache flushing) be made more aggressive (or disable it)? Or a setting to that effect? Currently I am left being unsure if my edits have been written down or not.
If you are using an external SDCard or portable hard drive, it's best to use the USB Icon in the Taskbar (lower right side of the taskbar) right click and "Eject" the disk. That will flush any chaching to the media.