Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Memory leak if log file is not writable #79

pheaver opened this Issue · 6 comments

2 participants


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 (


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!

@pheaver pheaver closed this

Thanks Philip!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.