SAP Knowledge Base Article - Preview

3129854 - Identifying and Troubleshooting a Memory Leak on JS Storefront in SSR Mode

Symptom

  1. Response time is increasing.
  2. The jsapps pods are restarting frequently.
  3. The logs show messages like below:
    • SSR rendering exceeded timeout 3000, fallbacking to CSR for /xyz
    • [PM2][WORKER] Process 0 restarted because it exceeds --max-memory-restart value (current_memory=4009730048 max_memory_limit=3865051136 [octets])
    • Rendering of /xyz was not able to complete. This might cause memory leaks!

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.


Read more...

Environment

JS Storefront on Commerce Cloud.

Product

SAP Commerce Cloud all versions

Keywords

spartacus;Server-Side Rendering;SSR;current_memory; max_memory_limit; , KBA , CEC-SPA , SAP Commerce Cloud Spartacus , How To

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.