Open csweichel opened 4 years ago
Werft seems to leak go-routines and memory over time. After running werft for about 72h and running about 200 jobs in that time, we have 9883 go routines. Memory consumption has rissen to about 136 megabytes.
This issue seems be related to the Subscribe handler not cleaning up properly, i.e. it doesn't react to context cancelation. See this pprof output:
Subscribe
Werft seems to leak go-routines and memory over time. After running werft for about 72h and running about 200 jobs in that time, we have 9883 go routines. Memory consumption has rissen to about 136 megabytes.