Interesting actually the new stack trace shows daemonStreamHandleWrite twice.
So it no more is the undefine call in this new code scenario.

Let me re-run this if that is always the case ...

Hmm, yeah it now always shows 2 times the stacks from daemonStreamHandleAbort.
Let me add that to my upstream mail ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822096

Title:
  libvirt hangs after utah workload is aborted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1822096/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to