Memory leaked when requiring nock

What is the expected behavior?

Nock should not keep any references that leaks memory.

What is the actual behavior?

Nock leaks memory as soon as it is required in a test.

How to reproduce the issue

Repro files: https://gist.github.com/avaly/8965470dfc5891836e57e2f95933f3cd

$ jest --detectLeaks
 FAIL  ./sum.test.js
  ● Test suite failed to run

    EXPERIMENTAL FEATURE!
    Your test suite is leaking memory. Please ensure all references are cleaned.

    There is a number of things that can leak memory:
      - Async operations that have not finished (e.g. fs.readFile).
      - Timers not properly mocked (e.g. setInterval, setTimeout).
      - Keeping references to the global scope.

      at node_modules/jest-cli/build/TestScheduler.js:240:24

As soon as the require('nock'); line is removed/commented out:

$ jest --detectLeaks
 PASS  ./sum.test.js
  ✓ adds 1 + 2 to equal 3 (2ms)

Versions

Software	Version(s)
Nock	10.0.6
Node	8.15.0

[eviltwin]

just for anyone coming across this today, it’s possible to clear up the leak by putting the following either in your test file or in your jest entry point:

afterAll(() => {
  // we must clean up nock and restore the http module to normal, otherwise
  // the tests will leak memory as it runs each test suite.
  nock.cleanAll()
  nock.restore()
})

[paulmelnikow]

I’m going to unpin this. Without a minimal test case, or even a very small test case with Jest, it’s hard to act on this.