Your server is running just fine, handling requests and sending responses. But then, ever so slowly, memory usage creeps up, and up, and up–until eventually your process runs out of memory and crashes. And then it restarts, and the leaking starts all over again.
In order to fix memory leaks, you need to figure out where that memory is being allocated. And that can be tricky, unless you use the right tools.
Let’s see how you can identify the exact lines of code that are leaking by using the Fil memory profiler.
Read more...from Planet Python
via read more
No comments:
Post a Comment