Before classifying this as a definite leak, it'd be good to work out some way to return control to the event loop for some period after this clean-up.
Cancelling a job is potentially an asynchronous operation, so the future returned by cancel() needs to be kept alive until the future is ready. We wait for this to happen by attaching a continuation to the future that will be called later in the event loop. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1634867 Title: Memory leak in DownloadJobImpl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/storage-framework/+bug/1634867/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
