Skip to content
Goroutine leak detector
Go Makefile
Branch: master
Clone or download
abhinav README: Mark as stable (#43)
Since we've tagged a 1.0, we can consider this library stable.

I've moved the stability section to the bottom since it's no longer
needed as a deterrent near the top.
Latest commit 8d7a168 Jan 10, 2020

goleak GoDoc Build Status Coverage Status

Goroutine leak detector to help avoid Goroutine leaks.


You can use go get to get the latest version:

go get -u

goleak also supports semver releases. It is compatible with Go 1.5+.

Quick Start

To verify that there are no unexpected goroutines running at the end of a test:

func TestA(t *testing.T) {
	defer goleak.VerifyNone(t)

	// test logic here.

Instead of checking for leaks at the end of every test, goleak can also be run at the end of every test package by creating a TestMain function for your package:

func TestMain(m *testing.M) {

Determine Source of Package Leaks

When verifying leaks using TestMain, the leak test is only run once after all tests have been run. This is typically enough to ensure there's no goroutines leaked from tests, but when there are leaks, it's hard to determine which test is causing them.

You can use the following bash script to determine the source of the failing test:

# Create a test binary which will be used to run each test individually
$ go test -c -o tests

# Run each test individually, printing "." for successful tests, or the test name
# for failing tests.
$ for test in $(go test -list . | grep "^Test"); do ./tests "^$test\$" &>/dev/null && echo -n "." || echo "\n$test failed"; done

This will only print names of failing tests which can be investigated individually. E.g.,

TestLeakyTest failed


goleak is v1 and follows SemVer strictly.

No breaking changes will be made to exported APIs before 2.0.

You can’t perform that action at this time.