Summary: | Large temp files with magick- prefix | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | P Tamas <supwphu> |
Component: | PS Interpreter | Assignee: | Default assignee <ghostpdl-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | critical | ||
Priority: | P4 | ||
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
URL: | https://stockvectorsillustrations.com/ | ||
Customer: | Word Size: | --- | |
Attachments: |
1 of the vectors
Jpeg |
Description
P Tamas
2020-04-18 11:18:51 UTC
The temp files are 19 GB in file size. Aren't deleted automatically. Created attachment 19157 [details]
1 of the vectors
Created attachment 19159 [details]
Jpeg
The command line shown has TWO input files, not one, but running the EPS file that was attached, I see that ghostscript creates only two temp files (for the command clist which handles the banded processing). The smaller "index" bfile was 302,608 bytes. The larger data file with the commands to allow banded rendering cfile was 110,898,625 bytes. Note that Ghostscript temp files are all created on linux using a method that opens, then unlinks the file so that even if the process aborts, the files do not exist. Note that the OutputFile is NOT deleted by Ghostscript, even if the process aborts. The full size output file in pamcmyk32 is 8,128,050,120 (7.5Gb). With the "%d" in the -sOutputFile string, there will be one of these for each page. Presumably, the second file creates a second page. As far as can be determined, Ghostscript is running as expected, and if the OutputFile 'pamcmyk32' format files created by Ghostscript are not being deleted, there is nothing that Ghostscript can do about it. Closing as WORKSFORME. Note that a debug build on my machine took 200 seconds and used 22Mb of RAM. |