SAS Web Application Server instances exhibit a memory leak in the compressed class space region, which prevents class metadata from being garbage collected.

The class space usage grows over time and eventually reaches the maximum limit, which is 1 GB by default. When this occurs, the SAS Web Application Server instance becomes unresponsive as it performs repeated full garbage collection cycles in an attempt to free memory. This issue can result in your SAS Web Applications being inaccessible or unresponsive.

If you are experiencing this issue, restarting the impacted SAS Web Application Server instance is a temporary workaround. The frequency at which this issue is experienced can depend on the usage of your environment. 

If you suspect that your environment is affected by this issue, contact SAS Technical Support for assistance and to determine a workaround plan. 

The hot fix for this issue is available for SAS^® 9.4M7 (TS1M7) in the SAS Security Update 2022-09 section on the SAS Security Updates and Hot Fixes page.