Since I switched to XWiki 10.1 (Windows 7 SP1, Tomcat 8.5.24) I experience OutOfMemoryExceptions despite the fact that I already increased to -Xmx6144m on the first occasion. Are there any known memory issue with the latest release?
Irrespective of any specific memory leaks have been officially identified, these kind of issues can appear due to these following underlying causes:
Large imports, document versions, or attachments consuming excessive memory
Extensions or custom Velocity macros holding onto memory longer than needed
Session bloat or unbounded caches
Inefficient memory usage patterns in long-running jobs or background tasks
In order to accurately identify the root cause of it, it's always better to capture a heap dump at the time of the error and analyze it using tools like the HeapHero, Eclipse Memory Analyzer Tool (MAT). The analysis report will help you identify the memory leaks, high-retention objects, or misconfigured caches.
You can have a look at this blog Beyond OutOfMemoryError: Using a Memory Analyzer for Subtle Memory Leaks for more practical guidance on how to perform such analysis and detect subtle memory leaks. Additionally, you can also try to enable the GC log which will provide trends about heap behavior over time, revealing whether the application is experiencing a slow memory leak or simply facing short-term spikes in usage.
