OOME when web content display portlet's configuration is opened

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.2.X, 7.3.X, Master
• Fix Version/s: 7.2.10 DXP FP11, 7.2.10.4 DXP SP4, 7.2.X, 7.3.10 DXP FP1, 7.3.10.1 DXP SP1, 7.3.6 CE GA7, 7.3.X, 7.4.13 DXP GA1, Master
• Component/s: Content Display Widgets > Web Content Display widget
• Labels:
  • ee-ts
  • liferay-dxp-72-sp4
  • liferay-dxp-73-sp1
  • liferay-fixpack-dxp-1-7310
  • liferay-fixpack-dxp-11-7210
• Branch Version/s:
  7.3.x, 7.2.x
• Backported to Branch:
  Committed
• Fix Priority: 3
• Git Pull Request: https://github.com/liferay-echo/liferay-portal/pull/3712

Reproduction Steps:

1. Create a web content structure containing a single Text field.
2. Create a template for that structure. The template should contain several rows (30 or so) of runtime JournalContentPortlets like this (added a template file):
   <@liferay_portlet["runtime"] portletName="com_liferay_journal_content_web_portlet_JournalContentPortlet" instanceId="testinst_1" />
3. Disable the Cacheable property on the template and save.
4. Create a web content using the structure created above. The field in the content does not need to be populated.
5. Place the content on a page. Several instances of empty JournalContentPortlets should appear on the page.
6. When opening the Configuration of the "outer" Web Content Display.

Expected behaviour: Configuration menu appears.
Actual behaviour: Liferay hangs running out of heap space.