Till, I already attached the CUPS error_log in #10 and #11.
Regarding which process takes up 100% CPU: it's the pdftoraster binary, althoug it shows up under the name of my printer in htop.
I tried to document this as best as I could in attachment #2:
If you search for 181498 in that file (the pid of the process which takes 100% CPU and lots of memory in that run) you'll find all the info I could glean from /proc/$pid/ about the process.
That's also how I came up with the arguments to pass to pdftoraster to try to isolate the cause of this issue.
(If you look at attachment #2, don't be confused about the name of the file being printed. This is not from printing the attached test files, but from the file where I first noticed the issue.)
Till, I already attached the CUPS error_log in #10 and #11.
Regarding which process takes up 100% CPU: it's the pdftoraster binary, althoug it shows up under the name of my printer in htop.
I tried to document this as best as I could in attachment #2:
If you search for 181498 in that file (the pid of the process which takes 100% CPU and lots of memory in that run) you'll find all the info I could glean from /proc/$pid/ about the process.
That's also how I came up with the arguments to pass to pdftoraster to try to isolate the cause of this issue.
(If you look at attachment #2, don't be confused about the name of the file being printed. This is not from printing the attached test files, but from the file where I first noticed the issue.)