@uj__: > The init process is certainly leaking memory. How have you proved that init is leaking memory? Can you say that PID 1 is not just still busy processing the flurry of events that would result from starting all these docker containers? Please provide further details.
> I've looked at the code and it seems like there may be some leaks. Where? > The upstart tests are are also leaking memory. Some of that memory is leaked > in the tests themselves (allocated and never freed) The tests may well leak memory as they are not designed to be long-running like upstart. > and some others seem to be leaking in libnih itself. Again, where? Please provide logs. Note that libnih goes to some lengths to avoid leaks by doing automatic garbage collection. If you can produce a test program demonstrating a leak, please attach to this bug so we can investigate further. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1198180 Title: possible leak in upstart 1.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1198180/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
