Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
The total ram is 60Kbytes, and not 64K as in the picture. If there is no application and no patches, then there is ~30Kbytes of free RAM. The actual amount of RAM used by the app depends on the app + patch code and statically allocated RAM + any dynamically allocated RAM for callback registrations, data buffers and memory pools. So adding a line of code can change this number quite dramatically (is it just a few instructions? Did it allocate RAM dynamically? Did it force the linker to pull in optional patches [some patches are linked in on-demand - if there is no reference to its API, it won't be linked in]?).
Instead of depending on a hard 'free RAM available for application', I suggest you determine this at run-time. At the end of your application create function, use cfa_mm_MemFreeBytes() to determine the number of free bytes till the end of RAM. Your application can grow (code + statically allocated memory + dynamic memory + patches) can grow by at most so many more bytes.