-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[Performance] Memory leak in Python #18749
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
Comments
Interestingly it worked in version onnx 1.8.1 and onnx runtime 1.6.0 (onnx/onnx#3293) |
If you look at the notebook, there is gc.collect after del |
This issue has been automatically marked as stale due to inactivity and will be closed in 30 days if no further activity occurs. If further support is needed, please provide an update and/or more details. |
This issue has been automatically closed due to inactivity. Please reactivate if further support is needed. |
Describe the issue
After deleting a session in python, the memory is still allocated (in the onnx runtime). Over time if multiple sessions are created this leaks to the memory getting overloaded. I attached a simple POC in colab
To reproduce
Further notebook:
https://colab.research.google.com/drive/1Q8OrYxt2PKGvXiWOw-LRjc7XV5mN7u1u#scrollTo=9UWHzgu76FaF
Urgency
This currently is crashing our production backend written in Python.
Platform
Linux
OS Version
Ubuntu 18.04
ONNX Runtime Installation
Released Package
ONNX Runtime Version or Commit ID
1.16.3
ONNX Runtime API
Python
Architecture
X64
Execution Provider
Default CPU
Execution Provider Library Version
No response
Model File
https://colab.research.google.com/drive/1Q8OrYxt2PKGvXiWOw-LRjc7XV5mN7u1u#scrollTo=9UWHzgu76FaF
Is this a quantized model?
Unknown
The text was updated successfully, but these errors were encountered: