https://github.com/uber-go/goleak

Goroutine leak detector
https://github.com/uber-go/goleak

Last synced: about 2 months ago
JSON representation

Goroutine leak detector

• Host: GitHub
• URL: https://github.com/uber-go/goleak
• Owner: uber-go
• License: mit
• Created: 2017-11-02T23:39:06.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2024-06-07T16:57:22.000Z (3 months ago)
• Last Synced: 2024-06-19T11:02:29.330Z (3 months ago)
• Language: Go
• Size: 104 KB
• Stars: 4,347
• Watchers: 45
• Forks: 144
• Open Issues: 10
• Metadata Files:
  • Readme: README.md
  • Changelog: CHANGELOG.md
  • License: LICENSE

Awesome Lists containing this project

• my-awesome - uber-go/goleak - 07 star:4.5k fork:0.1k Goroutine leak detector (Go)
• awesome-repositories - uber-go/goleak - Goroutine leak detector (Go)
• awesome-fancy-toolkit - Goroutine泄漏检测工具, goleak
• go-awesome - goleak - Goroutine leak detection (Open source library / Development Aid Package)
• awesome-tools - goleak - Goroutine leak detector to help avoid Goroutine leaks. (Programming / Go)

README

        
# goleak [![GoDoc][doc-img]][doc] [![Build Status][ci-img]][ci] [![Coverage Status][cov-img]][cov]

Goroutine leak detector to help avoid Goroutine leaks.

## Installation

You can use `go get` to get the latest version:

`go get -u go.uber.org/goleak`

`goleak` also supports semver releases.

Note that go-leak only [supports][release] the two most recent minor versions of Go.

## Quick Start

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

```go

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:

```go

func TestMain(m *testing.M) {

	goleak.VerifyTestMain(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:

```sh

# 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 -E "^(Test|Example)"); do ./tests -test.run "^$test\$" &>/dev/null && echo -n "." || echo -e "\n$test failed"; done

```

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

```

.....

TestLeakyTest failed

.......

```

## Stability

goleak is v1 and follows [SemVer](http://semver.org/) strictly.

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

[doc-img]: https://pkg.go.dev/badge/go.uber.org/goleak.svg

[doc]: https://pkg.go.dev/go.uber.org/goleak

[ci-img]: https://github.com/uber-go/goleak/actions/workflows/ci.yml/badge.svg

[ci]: https://github.com/uber-go/goleak/actions/workflows/ci.yml

[cov-img]: https://codecov.io/gh/uber-go/goleak/branch/master/graph/badge.svg

[cov]: https://codecov.io/gh/uber-go/goleak

[release]: https://go.dev/doc/devel/release#policy