Dan, I go back to my post on July 20 of last year when I was communicating with John Brock. Note in the lower entry for over an hour while I wasn’t working there was actually a slight decrease in the System data.
I started working at 8:54, finished at 19:36 and there was an increase of 23GB
@dan
OK, we might be on the road to tracking this down and looks like Rhino is not the culprit. No definitive answers yet but it looks as though the Operating System is taking regular snapshots of all of the data on the computer - not just Rhino files, with or without the complicity of Time Machine - and storing it somewhere out of view, presumably in the Systems Data.
My highly savvy technician is going to replace the hard drive next week and run some tests to see if he can be more specific about the cause of the problem. If he can I will happily share any information that might help to shed light on the issue - and, yes, walk back my suspicions that Rhino was to blame.
https://wiki.mcneel.com/rhino/mac/autosaving
Check this.
Yup, thanks, already been there!
Thank you for the update @tgra I’m glad progress is being made. I can definitely see why Rhino is implicated due to 3dm file sizes. (I’ve yet to encounter another macOS app that has files that can balloon as large as ours do that uses macOS Autosave/Versions).
Disk size aside, I’ve logged this bug (again!) to consider:
RH-71881 Autosave: Setting to toggle macOS Autosave/Versions
But I am still of two minds on this. My main concern - not the topic of this thread! - is file integrity.