JVM Heap Space out of memory - Where to start looking

My application is acquiring too much memory over time and therefore becomes slower and slower up to a point where it crashes. There does not seem to be a specific microflow that causes this, as sometimes the ''crash'' happens during the night when there are not any microflows running or users using the application. What is the best way to figure out which objects cause the memory to grow, or which objects stay in the memory which can be cleaned up (better).     Cache Image:
2 answers

You could create a support ticket so that when the above case is happening again they do a memory dump for you that can be analyzed. You might also double check after / before create microflows, because misconfigured ones can also cause these kind of strange behaviours.




Are you using any Java actions? That's where I would start looking first. What does the objects in memory overview in the cloud portal tell you?