Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Frequent OutOfMemory exceptions



The system is experiencing OutOfMemory exceptions frequently (about 1 - 2 a day). When they occur the system crashes and is restarted by the node agent.

Error Messages

Exception in thread "PegaRULES-Batch-16" java.lang.OutOfMemoryError: requested 140 bytes for CHeapObj-new. Out of swap space?

Steps to Reproduce


Root Cause

The JVM in question is a 32-bit JVM. 32-bit JVMs are limited to 4 GB of addressable memory space (based on the 32-bit architecture). The JVM settings was configured with a 2 GB maximum heap (Xmx), and 1 GB maximum permgen space. This meant there was only 1 GB remaining for native Java operations. This was insufficient in this environment and resulted in native OutOfMemory exceptions.


This issue was resolved by reducing the Xmx and MaxPermSize to allow more memory to be available for Java native processes.

Published June 12, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us