-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible memory leak when manually aborting an association #912
Comments
Yeah, there's some iffy behaviour in shutting the DUL down properly that will be fixed in the next release. |
Thanks! ETA for the next release? |
It'll be quite a while, I think. I've been focussing on pydicom's v3.0 release. |
In that case, what's your recommended approach? Is the proposed alternative a valid approach for now? |
Hey, any updates on this? |
Nothing so far, but probably soonish. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I have investigated a memory leak, which seems to be related to attempts of manually aborting associations.
Minimal example:
The above seems like a straight-forward way of aborting, but leads to leaking of DUL threads.
I have found that the below alternative works better:
The above approach is based on this.
I am wondering what is actually the best approach to abort an association at any time. Thoughts?
Originally posted by @pchristos in #652 (comment)
pydicom 2.3.1
pynetdicom 2.0.2
The text was updated successfully, but these errors were encountered: