Affects Version/s: 7.0.X, 7.1.X, 7.2.X, Master
Component/s: DM > Analytics
Liferay, by default, generates forked processes for Documents and Media preview generation according to the following property:
The problem is that there is currently no way to configure these forked processes further rising to the potential of memory leaks or issues that could cause the OOM Killer to kill the application server process that is running Liferay.
We only have ways to adjust the timeout, and to enable or disable forked processes, but no ways to adjust for resource allocation for these forked processes.
Note: There are potential security ramifications of this issue. A malicious actor could potentially upload a well-designed PDF to force an OOM on the Liferay process side (especially true in a DXPC instance where the server is running in a kubernetes setup.)
Steps to Reproduce
- Inspect portal.properties to check for any configurations that permit configuration of forked process resource allocation
We don't have the ability to limit or increase forked process resource allocation.
We need to have a way to limit or increase forked process resource allocation.
7.1.X Commit: f0dafe25c37a657b2abd3b905ee5f79ab5cb2712
Master Commit: 438ede3ce637a64c6011615666f9b0d566573926