This bug was fixed in the package cups - 2.2.11-0ubuntu1
---
cups (2.2.11-0ubuntu1) eoan; urgency=medium
* New upstream release
* Removed 10 patches taken from upstream.
* Refreshed 13 patches with quilt.
* Removed patch to set "LogDebugHistory 9" as it causes high
** Tags removed: rls-ee-incoming
** Tags added: rls-ee-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831021
Title:
Extremely high memory consumption under heavy workload
To manage
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831021
Title:
Extremely high memory consumption under heavy workload
To manage notifications about this bug go to:
Thank you for the explanation Till.
I believe the lack of previous complaints is because this happens in a
pretty unique conditions (very high MaxJobs and large batches of jobs).
The test case however was based on a real-life scenario reported to me.
--
You received this bug notification
I have raised the default LogDebugHistory some years ago as most
printing problems happen during the execution of a job and this way one
gets a logging with debug verbosity only for jobs and standard verbosity
for all the rest. This way one often did not need to ask the bug-
reporting users to
In a recent test with MaxJobs of 4 I was easily able to reach over
65 GB of memory consumption within 60 mins, while with LogDebugHistory
set to 0 the consumption was below 400 MB.
My recommendation is to lower the default LogDebugHistory value back to
what is upstream: 200.
--
You received
** Tags added: rls-ee-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831021
Title:
Extremely high memory consumption under heavy workload
To manage notifications about this bug go to:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (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/1831021
Title:
** Description changed:
Under heavy workload conditions cups can reach irrationally high memory
consumption very quickly (tens of GBs).
Test case:
1. Set MaxJobs to 4 in cupsd.conf.
2. sudo apt install cups-pdf
3. Fill the queue with jobs:
while [ 1 ]; lp -d PDF
After some analysis I believe the very high default value of
LogDebugHistory (9) is to blame for this (attaching massif report
from the test case).
With a high number of jobs it's very easy to get hunderds-thousands of messages
in LogDebugHistory which in turn will lead to enormous memory
10 matches
Mail list logo
