moby/plugin
Brian Goff eaad3ee3cf Make sure timers are stopped after use.
`time.After` keeps a timer running until the specified duration is
completed. It also allocates a new timer on each call. This can wind up
leaving lots of uneccessary timers running in the background that are
not needed and consume resources.

Instead of `time.After`, use `time.NewTimer` so the timer can actually
be stopped.
In some of these cases it's not a big deal since the duraiton is really
short, but in others it is much worse.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
2019-01-16 14:32:53 -08:00
..
executor/containerd libcontainerd: split client and supervisor 2018-08-06 10:23:04 -07:00
v2 Move plugin client creation to the extension point 2018-05-25 15:18:53 -04:00
backend_linux.go Various code-cleanup 2018-05-23 17:50:54 +02:00
backend_linux_test.go Add canonical import comment 2018-02-05 16:51:57 -05:00
backend_unsupported.go Switch from x/net/context -> context 2018-04-23 13:52:44 -07:00
blobstore.go Close readclosers returned by DecompressStream 2018-06-07 11:16:13 -07:00
defs.go Various code-cleanup 2018-05-23 17:50:54 +02:00
errors.go Add canonical import comment 2018-02-05 16:51:57 -05:00
events.go Add canonical import comment 2018-02-05 16:51:57 -05:00
manager.go Fix panic on daemon restart with running plugin 2018-06-07 17:27:02 -07:00
manager_linux.go Make sure timers are stopped after use. 2019-01-16 14:32:53 -08:00
manager_linux_test.go Update tests to use gotest.tools 👼 2018-06-13 09:04:30 +02:00
manager_test.go Add canonical import comment 2018-02-05 16:51:57 -05:00
manager_windows.go Fix panic on daemon restart with running plugin 2018-06-07 17:27:02 -07:00
store.go Various code-cleanup 2018-05-23 17:50:54 +02:00
store_test.go Add canonical import comment 2018-02-05 16:51:57 -05:00