You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered an issue in this otherwise excellent package, It appears that the connection to clamd is not being closed. I am running this on a Debian jessie system, with go v1.4.2. It's pretty easy to reproduce, just run the example from the README in a loop a thousand times, pause, and check the open files (e.g. using lsof).
Looking at the code, it appears that line clamd.go:282 is not firing:
wg.Wait()
On a whim, I changed the return value of conn.go:76 to return a pointer to the WaitGroup, on the hunch that the return value is being copied and so will never fire. This works.
I have encountered an issue in this otherwise excellent package, It appears that the connection to clamd is not being closed. I am running this on a Debian jessie system, with go v1.4.2. It's pretty easy to reproduce, just run the example from the README in a loop a thousand times, pause, and check the open files (e.g. using lsof).
Looking at the code, it appears that line clamd.go:282 is not firing:
On a whim, I changed the return value of conn.go:76 to return a pointer to the WaitGroup, on the hunch that the return value is being copied and so will never fire. This works.
Do you agree with my diagnosis?
The text was updated successfully, but these errors were encountered: