This appears to be a crash inside Qt itself, and only occurs with 5.6+, apparently due to QDBus changing to use threading instead of the event loop, for asynchronous operations. There seems to be some fixes in Qt Code Review that should theoretically fix this. It would be nice if we could test these and get them into our release of Qt. I'm afraid there won't be any way to work around this crash in the scope or ubuntu-download-manager (we're keeping a u-d-m singleton object around, which is destroyed on exit) code itself.
This appears to be a crash inside Qt itself, and only occurs with 5.6+, apparently due to QDBus changing to use threading instead of the event loop, for asynchronous operations. There seems to be some fixes in Qt Code Review that should theoretically fix this. It would be nice if we could test these and get them into our release of Qt. I'm afraid there won't be any way to work around this crash in the scope or ubuntu- download- manager (we're keeping a u-d-m singleton object around, which is destroyed on exit) code itself.