The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Problem/Motivation
When upgrading to version 5.0 and after configuring the /media view, I have observed that in the /tmp directory of the system, magick-* files are being generated within systemd-private-xxxxxxxxxxxxxxxxxxxxxxxx-httpd.servicexxx, which have a considerable size and do not they are deleted causing the file system to run out of available space.
Any idea why?
Thanks.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | realpath-fix-3292862-05.patch | 726 bytes | johankleene |
| #4 | realpath-fix-3292862-04.patch | 775 bytes | ayrmax |
Comments
Comment #2
jherpal98 commentedComment #3
johankleene commentedThis is still an issue, today disk was full, caused by huge amount of magick-... files in the tmp directory.
Comment #4
ayrmax commentedSteps to reproduce
Generate a PDF Image of a PDF with 160 or more pages.
Proposed resolution
The Media PDF Thumbnail Module utilizes the URI instead of the realpath. For instance, it employs the format public://foo/bar.pdf.
When the path is remote, the spartie/pdf-to-image library generates images for every page of the PDF. It verifies whether the path is remote by using the
filter_var($path, FILTER_VALIDATE_URL)function. However, when a Drupal URI is provided, the spartie/pdf-to-image library mistakenly considers the file as remote and proceeds to generate images for all pages.Consequently, when dealing with PDF files that contain numerous pages, imagick consumes a significant amount of temporary space on the server.
I provided a patch to fix the issue.
Comment #5
johankleene commentedUsed the previous fix and the problem did not return.
Patch does not apply against version 6.0.0-rc2, so this is a reroll against 6.0.0-rc2.
Comment #6
sgostanyan commentedMerged in 6.0.0-rc3
Thanks