Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix a memory leak related to ExecutionContext and Promises #2215

Merged
merged 4 commits into from
Jun 21, 2022

Conversation

kamilkisiela
Copy link
Collaborator

Fixes #2150

@changeset-bot
Copy link

changeset-bot bot commented Jun 20, 2022

🦋 Changeset detected

Latest commit: d408370

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
graphql-modules Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link

vercel bot commented Jun 20, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
graphql-modules ✅ Ready (Inspect) Visit Preview Jun 21, 2022 at 3:00PM (UTC)

@theguild-bot
Copy link

theguild-bot commented Jun 20, 2022

The latest changes of this PR are available as alpha in npm (based on the declared changesets):

graphql-modules@2.0.1-alpha-b5f76c3d.0

@kamilkisiela kamilkisiela merged commit 285987c into master Jun 21, 2022
@kamilkisiela kamilkisiela deleted the kamil-execution-context-memory-leak branch June 21, 2022 15:04
@Multiply
Copy link

Multiply commented Jul 5, 2022

Thank you so much for this fix! We've been hunting memory leaks for a while, and quickly figured it out to be our apollo-server contexts not being cleaned up, and suspected graphql-modules, but couldn't easily spot why.

Graph of memory usage over the last week, and then after applying the fix:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Possible memory leak if context keep reference to a promise
3 participants