(In reply to comment #15)
> What is the plan for handling this in breezy? I don't see how the release can
> ship with a leak like this.
It only seems to affect a few users, the cause is unknown, and there is a simple
workaround available. If someone can track down the leak, it's possible that we
can squeeze in a fix before the final release, but it won't be delayed on
account of this bug.
(In reply to comment #15)
> What is the plan for handling this in breezy? I don't see how the release can
> ship with a leak like this.
It only seems to affect a few users, the cause is unknown, and there is a simple
workaround available. If someone can track down the leak, it's possible that we
can squeeze in a fix before the final release, but it won't be delayed on
account of this bug.