KRC1030

Common Causes

• KRL program contains excessively large arrays or data structures that consume too much memory
• Memory leak caused by recursive function calls without proper termination conditions
• Multiple instances of heavy objects or modules loaded simultaneously without cleanup
• Dynamic memory allocation in loops without corresponding deallocation or garbage collection
• Program attempting to load or instantiate objects beyond the virtual memory pool capacity of 2800 units

Troubleshooting Steps

1. 1Review the KRL program object name specified in the alarm to identify which module, function, or variable is causing the memory issue
2. 2Optimize data structures by reducing array sizes, using local variables instead of global ones, and eliminating unnecessary object instantiation
3. 3Check for infinite loops or recursive function calls that may be allocating memory without releasing it
4. 4Split large programs into smaller modules and load them sequentially rather than simultaneously to reduce peak memory usage
5. 5Clear unused variables and deallocate memory explicitly where possible, especially after completing operations with large datasets
6. 6Restart the KRC controller and reload the program to reset the virtual memory state, then monitor memory usage during execution