Skip to content
This repository

Memory leak if log file is not writable #79

pheaver opened this Issue · 6 comments

2 participants

Philip Weaver Gregory Collins
Philip Weaver

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 (

Gregory Collins

Should be fixed as of snap-server commit 304b7ad. Please confirm?

Philip Weaver

Ok, I'll take a look at it, thanks.

Gregory Collins

Ping? Is it fixed?

Philip Weaver

Will look at it tonight or tomorrow.

Philip Weaver

Looks like it's fixed!

Philip Weaver pheaver closed this
Gregory Collins

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.