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).
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!