Comment 29 for bug 1655169
Revision history for this message
| Anastasia (anastasia-macmood) wrote | #29 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
@Chad Smith (chad.smith),
We are aware of the residual and minor memory leaks in 2.1. The workaround for these is to restart jujud occasionally via cron job. Majority of improvements did go into 2.1.x, hence, the Fix Released status on this report.
These are being fixed in Juju 2.2. The fix requires a dependent websocket library update and will not be backported to previous Juju versions. We are tracking the progress of this work through bug # 1649719.
If you are experiencing further memory leaks with 2.2x, please file a separate bug rather than morph this one.