Acting on 'out of memory'
-
THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED
On 15/01/2008 at 11:39, xxxxxxxx wrote:
User Information:
Cinema 4D Version: R9-R10
Platform: Windows ; Mac ; Mac OSX ;
Language(s) : C++ ;---------
I see that there is a Safety class which can be used when possibly working in low memory situations but am not certain that it would be useful (only backs up tags?).There are situations where the memory (from copies or undos or who knows) just grows disproportionately to what is being done and *poof* you are out of memory. It would be great to be capable of doing *something* in these circumstances (go back like Safety or save the document in a hurry).
To be crystal clear here - there is absolutely no possible way that I can reduce the memory usage of the plugin. I've already been down this road - the undo storage is as optimal as I can get and still have viable undos. I've block allocated as much memory as possible (instead of a bazillion little allocations). Arrays are stored z-lib compressed in memory (wish I could do the same for C4D stuff!) and are decompressed into a single-purpose expansion buffer.
The question is: When I can do nothing else to keep from running out of memory, what can I do when it happens (besides displaying errors and returning FALSE to no avail)?
Thanks,