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
Memory leak if log file is not writable #79
Comments
Should be fixed as of snap-server commit 304b7ade452c9d844ac27b8d44769db33049b0c9. Please confirm? |
Ok, I'll take a look at it, thanks. |
Ping? Is it fixed? |
Will look at it tonight or tomorrow. |
Looks like it's fixed! |
Thanks Philip! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the location of the access log is not writable, Snap's memory footprint grows with each request that it tries to log.
I don't think there's any other information needed to reproduce this problem. It happens on multiple versions of Snap, including the latest (0.5.4.1).
The text was updated successfully, but these errors were encountered: