Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upMemory leak in uvloop and tornado #252
Open
Labels
Comments
|
Hi! There have been several fixes related to memory leaks since uvloop 0.11.1. Could you please try 0.13.0rc1 and let us know if the leak still occurs? |
|
Hi, thank you, i try this and report then! |
|
Did you get a chance to retest? |
|
Sorry, i forget this. I fix my another problem and this not check with another uvloop. In this holidays i repeat my experiment, and report it. |
|
@totaki any update on this? |
|
Was everything all good with this in the end? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
PYTHONASYNCIODEBUGin env?: This no effectI have a platform to which mobile devices will constantly connect via TCP, about 20k per instance. After a few hours of work, memory consumption rises to 2 GB. We use tornado 5.0.1 as TCP server and install uvloop for loop for asyncio. I conducted one experiment using tracemalloc, when the devices are disconnected and then the memory leak is again connected in this code line , the number of objects and the total expanding. Can you help find what these objects are and how to remove this leak?
