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:-
I am seeing the same behaviour in terms of CPU usage and time taken. A
14 page pdf took close to 4 minutes to print and all the while
pdftoraster process was utilizing 100% CPU as per "top".
I'm using Pop!_OS 21.04 - happy to provide any logs etc.
--
You received this bug notification because
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
@Pratyush: I'll try in the next days.
What's the recommended way of doing this on Ubuntu? Can I compile using make
and then just copy over the single pdftoraster binary, or should I do a full
make install?
I also commented on your pull request on the OpenPrinting github repo.
There seem to be a
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
@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
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
Manu, which is the process which takes up 100% CPU? It could be the
blocking one.
The other qustion is what is the output of pdftoraster? Perhaps the
raster data is in another than the expected resolution or color depth
(too high) and so any subsequent filter or the printer take too long to
@Till and Pratyush, any idea, on top of this issue, what might be
causing printing to take so much longer than just the runtime of
pdftoraster (10 minutes vs 17 seconds)?
I see a single process taking up 100% of one cpu in htop all the while.
--
You received this bug notification because you
Sure, I am looking into it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920190
Title:
Printing to ipp printer uses multiple GB of ram. pdftoraster and/or
filter chain selection at fault?
To
Manu, yes this link is pointing to the actual source code of the
pdftoraster filter.
Pratyush, can you investigate whether this source code has memory leaks?
Perhaps after finishing each page end sending it off one could free the
memory of that page.
--
You received this bug notification
@Till, thanks for the heads-up. pdftoraster is the one that came installed
automatically, I didn't install anything manually.
(manu@lari:~$ dpkg -S /usr/lib/cups/filter/pdftoraster
cups-filters-core-drivers: /usr/lib/cups/filter/pdftoraster)
@Pratyush, 30% of 4GB is around 1.3GB, which is close
Pratyush, all libraries which pdftoraster needs should be already
installed, if only one is missing, pdftoraster does not run at all. So
adding any libraries does not add any new features. Especially if Manu's
pdftoraster is installed as part of the cups-filters package of Ubuntu,
all needed
@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
@Pratyush:
I had to guess/google package names, but running
sudo apt install libpoppler-cpp-dev poppler-utils liblcms2-2
libfreetype6 fontconfig libjpeg-tools libtiff-tools zlibc libpng-tools
gave:
The following NEW packages will be installed:
libjpeg-tools libpoppler-cpp-dev
@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
manu@lari:~$ lpstat -a
Brother_MFC_L2710DW_series accepting requests since Mon 19 Apr 2021 10:46:49
followme accepting requests since Wed 11 Dec 2019 17:27:19
manu@lari:~$ lpstat -v
device for Brother_MFC_L2710DW_series:
implicitclass://Brother_MFC_L2710DW_series/
device for followme:
@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
** Attachment added: "'tail -f -c 0 /var/log/cups/error_log > error_log_48'
while printing test48.pdf"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920190/+attachment/5488475/+files/error_log_48
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@Pratyush
I attached both logs as seperate files. I only put 3 sheets of paper in the
tray each time and cancelled on the printer once those were out, as I didn't
want to print that many useless pages, but as the processing happens before the
printer starts printing I think this shouldn't
** Attachment added: "'tail -f -c 0 /var/log/cups/error_log > error_log_12'
while printing test12.pdf"
https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1920190/+attachment/5488474/+files/error_log_12
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@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:-
For anyone looking for a workaround: Installing the driver from the
Brother website worked for me. It appears this solution might not
continue to work, however, because driver installation includes the
following message:
"lpadmin: Printer drivers are deprecated and will stop working in a
future
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups-filters (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920190
I'm having the same problem on a Brother HL-L2370DW printer on 21.04. My
machine has 32GB of memory but has trouble printing longer documents.
After hitting "print", memory usage continues creeps up over a long
period of time and consumes a lot of memory. I believe the OOM killer
killed
** Summary changed:
- When printing to ipp printer, multiple GB of ram are used. pdftoraster and/or
filter chain selection at fault?
+ Printing to ipp printer uses multiple GB of ram. pdftoraster and/or filter
chain selection at fault?
--
You received this bug notification because you are a
26 matches
Mail list logo
