On Thu, Feb 22, 2018 at 08:33:19PM -0000, sean wrote:
> I feel that sssd_be spiraling out of control (spawning hundreds to
> thousands of processes) and consuming all of the available RAM would be
> considered a "High-impact" bug, when that same behavior is not observed
> in 14.04.

Indeed, which is why I explained what process to follow to get the bug
fixed in xenial-updates for 16.04 in comment 2.

> 16.04 has a xenial-backport component, is it not possible to put a newer
> version there instead of placing it in xenial-updates or xenial-
> security?

Sure, if somebody follows the process, prepares a suitable upload, and
so forth. Somebody will also need to continue maintaining the backports
package for security, assuming you care about that, since Canonical's
security cover doesn't cover the backports pocket. But in any case this
is a bug, so fixing it in xenial-updates would be preferable.

>           What dictates what is put where? If upstream never releases
> 1.13.5 (though they seem to have tagged this 1.13 release:
> https://github.com/SSSD/sssd/releases/tag/sssd-1_13_91), will 16.04
> never get an sssd upgrade?

Did you read https://wiki.ubuntu.com/StableReleaseUpdates? We absolutely
can update sssd in xenial-updates in 16.04 to fix this bug. Somebody
just needs to figure out the appropriate fix and follow the process to
get the fix landed.

Right now, I note that only two people have reported themselves as
affected and the bug has been open a year. We don't have specific steps
to reproduce the problem, and no specific fix has been identified. So it
seems to me rather difficult to tackle for someone who does not know how
to reproduce the problem. But if someone affected can find the required
development effort to fix this, Ubuntu will welcome that contribution.

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  sssd_be is leaking memory

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to