Canonical Juju

Memory/goroutine leaks.

Bug #1516669 reported by Eric Snow on 2015-11-16

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical Juju	Fix Released	High	Unassigned	Canonical Juju 2.1-rc1

lp:1382556 indicates that there are likely a number of memory/goroutine leaks in juju that contribute to juju's high memory usage.

Addressing any remaining high memory usage in juju, aside from leaks, should be addressed separately if necessary.

Tags:

Cheryl Jennings (cherylj) on 2015-11-16

Cheryl Jennings (cherylj) on 2015-12-10

Changed in juju-core:
milestone:	2.0-alpha1 → 2.0-beta1

Revision history for this message

Katherine Cox-Buday (cox-katherine-e) wrote on 2016-01-05:

Possibly related: bug 1519473

Curtis Hovey (sinzui) on 2016-02-19

Changed in juju-core:
milestone:	2.0-beta1 → 2.0-beta2

Curtis Hovey (sinzui) on 2016-03-10

Changed in juju-core:
milestone:	2.0-beta2 → 2.0-beta3

Curtis Hovey (sinzui) on 2016-03-25

Changed in juju-core:
milestone:	2.0-beta3 → 2.0-beta4

Cheryl Jennings (cherylj) on 2016-04-05

Changed in juju-core:
milestone:	2.0-beta4 → 2.1.0

Canonical Juju QA Bot (juju-qa-bot) on 2016-08-22

Revision history for this message

Anastasia (anastasia-macmood) wrote on 2017-02-08:

We have addressed several memory leaks in recent Juju releases, including the ones currently under development.

I am closing this bug as it is not specific enough and its original cause may have been addressed.

Curtis Hovey (sinzui) on 2017-02-22

Changed in juju:
status:	Fix Committed → Fix Released

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Bug watches keep track of this bug in other bug trackers.