Comment 3 for bug 1868362

That said, the only one we've monitored closely and taken big iterations on
is the controller agent. I believe on prodstack we actively take goroutine
and heap dumps so we can look for memory leaks after the fact. We could
potentially do something like that for a couple of the unit agents,
(something like a cron that calls juju_heap_profile and saves the result
somewhere we can look at it afterward.

On Mon, Mar 23, 2020 at 9:15 AM Ian Booth <email address hidden> wrote:

> We've fixed a few leaks in 2.7 compared to 2.6, eg in 2.6 there's a
> goroutine leak that can be triggered under the right circumstances.
>
> Just to set expectations, we don't plan on anymore 2.6 releases
> unfortunately.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1868362
>
> Title:
> Memory leak in jujud agents
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1868362/+subscriptions
>