Out of memory due to package build

[vishwanath881]

Hello Team,

I tried to build a package with many filters(around 20) from crx package manager. But, the package build has taken a lot of time and eventually I refreshed the browser to stop it. I believe that all the filters were of small size and the whole package on the whole should also be small in size(after build).

After this our instance has gone into Out of memory (java.lang.OutOfMemoryError: GC overhead limit exceeded).

Could you please help us with this ?

[askdctm]

Hi vishwanath,

Whenever we encountered an OOM error, we had no other choice but to restart the instance.

[kautuk_sahni]

Hi

Please have a look at following KB/Troubleshooting articles:-

AnalyzeMemoryProblems https://helpx.adobe.com/experience-manager/kb/AnalyzeMemoryProblems.htmlAnalyzeSlowAndBlockedProcesses https://helpx.adobe.com/experience-manager/kb/AnalyzeSlowAndBlockedProcesses.html

AnalyzeSlowAndBlockedProcesses https://helpx.adobe.com/experience-manager/kb/AnalyzeSlowAndBlockedProcesses.html

crx-disk-and-memory-monitoring-shutdown-too-aggressively https://helpx.adobe.com/experience-manager/kb/crx-disk-and-memory-monitoring-shutdown-too-aggresivel...
CRX throws out-of-memory errors https://docs.adobe.com/docs/en/aem/6-0/administer/operations/troubleshoot.html

I hope this would help you.

Thanks and Regards

Kautuk Sahni

[Jörg_Hoh]

Hi,

how many nodes are being put into the package? And what is your JVM heapsize?

kind regards,
Jörg

[Lokesh_Shivalingaiah · Accepted solution]

I dont think it matter on the number of filters in the package. How many resources or nodes are you packaging withing those filters. Are there any big size assets with it ?

Also as Josh mentioned, whats your JVM heapsize ?