The bug post was about excessive RAM usage leading to swapping. High CPU usage
shouldn't be a problem. Moreover pdftoraster takes more time than other
filters. Try using gstoraster for faster compilation.
The original issue was resolved here:-
https://github.com/OpenPrinting/cups-filters/pull/36
I would recommend to clone the repo and then install it. "pdftoraster"
currently runs as a standalone executable but I believe a simple
replacement of pdftoraster located in "usr/lib/cups/filter" with the
upstream file won't do the job.
I am sure that you will end up with the color case and not wi
Tested this command on an another system and still got about 100s
runtime.
/usr/bin/time -v /usr/lib/cups/filter/pdftoraster 99 manu sometitle 1
'PageSize=A4 output-format=apple-raster Resolution=600dpi'
testdoc/test12.pdf > pdftorast.out
--
You received this bug notification because you are a m
@manu
There has been a recent pull request about this issue :-
https://github.com/OpenPrinting/cups-filters/pull/363
I believe this would solve the issue of monotonous increase of ram
usage. Please try this and let me know.
I also checked the error_log attached by you closely.
So your print queu
Sure, I am looking into it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-filters in Ubuntu.
https://bugs.launchpad.net/bugs/1920190
Title:
Printing to ipp printer uses multiple GB of ram. pdftoraster and/or
filter chain selec
@manu
Yes pdftoraster uses higher memory. For the test12.pdf it consumed about 30%
RAM for a 4GB OS. It also takes significant time to do the job but it is way
more for your case. This will be sorted out soon in the next releases of
cups-filters which would be coming with cups package for debian
@manu
So actually pdftoraster takes significant time and uses significant ram while
processing. But it is using way too much in your case. This is because
pdftoraster comes with extended features. Whereas gstoraster is quite fast and
it also does not hog this much of memory. Although CPU utiliza
@manu
Can you please run the command "lpstat -a" and "lpstat -v" in terminal and
attach the listed output here.
In the error log I can see lots of these statements "HTTP_STATE_WAITING Closing
for error 32 (Broken pipe)". This is typically related with cups-browsed not
able to find print destina
@Manu
Can you please attach the error_log too. It is located in the var/log/cups
directory.
Please make sure to enable the log level to debug or debug2 before uploading.
You can get an idea about how to do it in the following link:-
https://www.thegeekdiary.com/how-to-enable-cups-debugging-on-c
9 matches
Mail list logo