It is possible we're leaking memory, but if you're working for hours on end, memory fragmentation might also explain part of the increase. I've been fiddling with the file for about 10 minutes and it climbed from 1.7 GB to 1.9GB, but then I've been switching previews on which means more meshes get calculated so you'd expect a higher memory consumption. I try to only keep about 2 curves turned on. The GH file we're talking about is 7Mb & the Rhino file is about 120Mb, but when working w/ the GH def. I think what I've learned from this is that one should limit the size of the GH file, or put some incremental stops in the definition to limit the length of calculations that it runs at once. ![]() This is in relation to a discussion I've been having with David Rutten & Scott Davidson about GH consuming memory in a relatively large GH definition (~. Also, what is the procedure to change it back to a usable GH file? Simply change the extension back to. ![]() GH crashed & I really could use that last autosave file. ![]() I am trying to retrieve an autosave file.
0 Comments
Leave a Reply. |