Details
-
Improvement
-
Resolution: Unresolved
-
Normal
-
None
-
3.5.5
-
None
Description
Magnolia is using different classes in the dam-app and in the dam chooser for generating thumbnail views:
dam-app uses info.magnolia.dam.app.contentview.column.JcrAssetNameColumnDefinition
dam-chooser uses info.magnolia.dam.app.contentview.column.AssetNameColumnDefinition
The dam-app class used the the imaging portrait generator to show the thumbnails.
The dam-chooser class could use the imaging provider as well and uses default as generator. The thumbnails are related to the 240 variation which is available in the travel demo theme. If this variation doesn't exist (for example if you don't install the travel demo), then you will fallback to the default original which can be a 10Mb size image
This is a problem because if you have some hundreds assets (>10mb) and you open a chooser dialog without a 240 thumbnail image variation (within your theme), then instead of using the default thumbnail generator for creating the variant, it will reduce the original image (which is quite large in size) and the asset chooser will become unresponsive (and in some cases, can crash the instance).
So if you have the 240 variant defined, the asset-chooser will load:
/.imaging/mte/travel-demo-theme/240/dam/myBigImage.jpeg/jcr:content/myBigImage.jpeg
But if you don't have it defined, it will load original image:
/.imaging/default/dam/myBigImage.jpeg/jcr:content.jpeg
For the same preview (thumbnail), the dam app uses:
/.imaging/portrait/dam/37c19a57-24c7-4467-abd4-65d73d48da15/myBigImage.jpeg.2022-12-02-13-30-41.jpg