ci/circleci: browser
Your tests passed on CircleCI!
Details
ci/circleci: browserstack
Your tests passed on CircleCI!
Details
ci/circleci: lint
Your tests passed on CircleCI!
Details
ci/circleci: node-amqp10
Your tests passed on CircleCI!
Details
ci/circleci: node-amqplib
Your tests passed on CircleCI!
Details
ci/circleci: node-bench-e2e-latest
Your tests passed on CircleCI!
Details
ci/circleci: node-bench-latest
Your tests passed on CircleCI!
Details
ci/circleci: node-bench-profiler-latest
Your tests passed on CircleCI!
Details
ci/circleci: node-bluebird
Your tests passed on CircleCI!
Details
ci/circleci: node-bunyan
Your tests passed on CircleCI!
Details
ci/circleci: node-cassandra
Your tests passed on CircleCI!
Details
ci/circleci: node-connect
Your tests passed on CircleCI!
Details
ci/circleci: node-core-10
Your tests passed on CircleCI!
Details
ci/circleci: node-core-12
Your tests passed on CircleCI!
Details
ci/circleci: node-core-14
Your tests passed on CircleCI!
Details
ci/circleci: node-core-15
Your tests passed on CircleCI!
Details
ci/circleci: node-core-8
Your tests passed on CircleCI!
Details
ci/circleci: node-core-latest
Your tests passed on CircleCI!
Details
ci/circleci: node-core-windows
Your tests passed on CircleCI!
Details
ci/circleci: node-couchbase
Your tests passed on CircleCI!
Details
ci/circleci: node-dns
Your tests passed on CircleCI!
Details
ci/circleci: node-elasticsearch
Your tests passed on CircleCI!
Details
ci/circleci: node-express
Your tests passed on CircleCI!
Details
ci/circleci: node-fastify
Your tests passed on CircleCI!
Details
ci/circleci: node-fs-10
Your tests passed on CircleCI!
Details
ci/circleci: node-fs-12
Your tests passed on CircleCI!
Details
ci/circleci: node-fs-14
Your tests passed on CircleCI!
Details
ci/circleci: node-fs-15
Your tests passed on CircleCI!
Details
ci/circleci: node-fs-8
Your tests passed on CircleCI!
Details
ci/circleci: node-fs-latest
Your tests passed on CircleCI!
Details
ci/circleci: node-generic-pool
Your tests passed on CircleCI!
Details
ci/circleci: node-google-cloud-pubsub
Your tests passed on CircleCI!
Details
ci/circleci: node-graphql
Your tests passed on CircleCI!
Details
ci/circleci: node-grpc
Your tests passed on CircleCI!
Details
ci/circleci: node-hapi
Your tests passed on CircleCI!
Details
ci/circleci: node-http
Your tests passed on CircleCI!
Details
ci/circleci: node-http2
Your tests passed on CircleCI!
Details
ci/circleci: node-knex
Your tests passed on CircleCI!
Details
ci/circleci: node-koa
Your tests passed on CircleCI!
Details
ci/circleci: node-memcached
Your tests passed on CircleCI!
Details
ci/circleci: node-microgateway-core
Your tests passed on CircleCI!
Details
ci/circleci: node-mongodb-core
Your tests passed on CircleCI!
Details
ci/circleci: node-mongoose
Your tests passed on CircleCI!
Details
ci/circleci: node-mysql
Your tests passed on CircleCI!
Details
ci/circleci: node-net
Your tests passed on CircleCI!
Details
ci/circleci: node-paperplane
Your tests passed on CircleCI!
Details
ci/circleci: node-pino
Your tests passed on CircleCI!
Details
ci/circleci: node-postgres
Your tests passed on CircleCI!
Details
ci/circleci: node-promise
Your tests passed on CircleCI!
Details
ci/circleci: node-promise-js
Your tests passed on CircleCI!
Details
ci/circleci: node-q
Your tests passed on CircleCI!
Details
ci/circleci: node-redis
Your tests passed on CircleCI!
Details
ci/circleci: node-restify
Your tests passed on CircleCI!
Details
ci/circleci: node-router
Your tests passed on CircleCI!
Details
ci/circleci: node-tedious
Your tests passed on CircleCI!
Details
ci/circleci: node-when
Your tests passed on CircleCI!
Details
ci/circleci: node-winston
Your tests passed on CircleCI!
Details
ci/circleci: typescript
Your tests passed on CircleCI!
Details
What does this PR do?
Fix memory leak in the async_local_storage scope manager.
Motivation
There is a bug in
AsyncLocalStoragewhereenterWithmay be called while in the callback ofexit, causing the storage instance to be re-added to the internal storage list. This slows down the application continuously until it's no longer able to respond to requests. A fix will need to be done in Node, but in the meantime we can simply remove our call toexitsince it was just an optimization that is unnecessary.Fixes #1133