hasura / hasura/graphql-engine

Memory leak

Open
#9,592 68 comments 14 reactions 0 assignees View on GitHub
k/bug t/gql-services
Dominant language
TypeScript
Stars
32.1k
Forks
3k
PR merge metrics
PR metrics pending

Description

### Version Information

Server Version: v2.22.1
CLI Version (for CLI related issue):

### Environment

On-premises

### What is the current behaviour?

We've been seeing memory leaks since version v2.19.x and higher

Upgrading to the latest version did not solve the problem, version v2.8.4 works correctly.

### What is the expected behaviour?

To work without memory leaks

### How to reproduce the issue?

1. Upgrade to 2.19.x and higher.

### Screenshots or Screencast

Screenshot 2023-04-17 at 09 41 33

OOM:
image

### Please provide any traces or logs that could help here.

### Any possible solutions/workarounds you're aware of?

### Keywords

memory leak

Contributor guide

Open the contributing guide

Research direction

Start by comparing the on-premises server behavior between v2.8.4 and v2.19.x or later, using the supplied screenshots and a reproduction that reaches OOM. Collect traces or logs and narrow the leak to a server component; done means the cause is identified and the server no longer leaks memory under the reproducing workload.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
api, backend, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.