Memory leak if log file is not writable #79

Closed
pheaver opened this Issue Jul 5, 2011 · 6 comments

Comments

Projects
None yet
2 participants
@pheaver

pheaver commented Jul 5, 2011

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

@gregorycollins

This comment has been minimized.

Show comment
Hide comment
@gregorycollins

gregorycollins Aug 14, 2011

Member

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

Member

gregorycollins commented Aug 14, 2011

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

@pheaver

This comment has been minimized.

Show comment
Hide comment
@pheaver

pheaver Aug 14, 2011

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

pheaver commented Aug 14, 2011

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

@gregorycollins

This comment has been minimized.

Show comment
Hide comment
@gregorycollins

gregorycollins Sep 12, 2011

Member

Ping? Is it fixed?

Member

gregorycollins commented Sep 12, 2011

Ping? Is it fixed?

@pheaver

This comment has been minimized.

Show comment
Hide comment
@pheaver

pheaver Sep 12, 2011

Will look at it tonight or tomorrow.

pheaver commented Sep 12, 2011

Will look at it tonight or tomorrow.

@pheaver

This comment has been minimized.

Show comment
Hide comment
@pheaver

pheaver Sep 13, 2011

Looks like it's fixed!

pheaver commented Sep 13, 2011

Looks like it's fixed!

@pheaver pheaver closed this Sep 13, 2011

@gregorycollins

This comment has been minimized.

Show comment
Hide comment
@gregorycollins

gregorycollins Sep 13, 2011

Member

Thanks Philip!

Member

gregorycollins commented Sep 13, 2011

Thanks Philip!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment