KNOWLEDGE BASE
Log In    |    Knowledge Base    |    4D Home
Tech Tip: Reassess Stack Size Assignments for Processes When Upgrading
PRODUCT: 4D | VERSION: 18 | PLATFORM: Mac & Win
Published On: January 11, 2021

With new hardware standards being set, applications are improved to take advantage of these resources. Such as the move from 32-bit architectures to 64-bit architectures. Another resource that has become more available is memory.

Newer 64-bit versions of 4D may require more memory for the same processes but can generate improvements by doing so. Some commands allow the stack to be declared such as New Process and Execute on server. In older versions of 4D the stack would need to be declared, with newer versions of 4D a value of "0" can be passed which will allow the application to automatically allocate memory needed to run the processes.

If a recently upgraded database is encountering errors relating to the "Stack" or "Memory", such as the Stack being full, the issue may be related to the process not having enough memory allocated due to a specific value being assigned.

If the process process's initiating method should be identified and the memory should be increased or set to "0". Unfortunately, debugging the process will not show the initiating command. Some tricks to use are to search for the method's name or if the process has a unique name, the name should have been passed as a parameter to the initiating command.