You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The maintainer responded with the assumption that the increased memory usage may not be a true memory leak, but rather due to how Python's garbage collector works in combination with how the library is used (especially in the main process or without proper scoping).
They suggest wrapping memory-heavy calls in separate functions to allow Python to release memory more effectively, and confirmed that freeMemory() should be called to help clean up.
When making requests that return large responses, memory usage goes through the roof. It doesn’t seem to scale properly with the response size.
Script to reproduce
Output
Expected Behavior
A 73MB response shouldn’t cause memory usage to jump by over 1GB. Some increase is expected, but this seems excessive.
The text was updated successfully, but these errors were encountered: