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

Pooled connections memory leaks upgrading past 3.9.4 #3202

Open
adminDelcom opened this issue Nov 12, 2024 · 0 comments
Open

Pooled connections memory leaks upgrading past 3.9.4 #3202

adminDelcom opened this issue Nov 12, 2024 · 0 comments

Comments

@adminDelcom
Copy link

adminDelcom commented Nov 12, 2024

Using pooled connections, we upgraded from 3.9.4 to 3.11.3 and instantly saw huge memory leaks in many deployed production enviroments. See screenshots below from google cloud run where the line with the i and dotted lines marks the deployment of the libary 3.11.3. Its very clear that its the changes between 3.9.4 and 3.11.3

Screenshot of container insights in production after deployement
383277311-f3291061-cb36-4996-a0bd-8fdf803be781

I downgraded to 3.9.7 and still have the memory leaks.

Rolling back to mysql 3.9.4 solves the issue

We are using typeorm but the mysql config parms are just passed down. I will write the relevant ones below;

{
          type: xxxx,
          username: xxxx,
          password: xxxx,
          database: xxxx,
          entities: dmsDbEntities,
          synchronize: false,
          pool: {
            max: 25,
            min: 0,
          },
          extra = {
            socketPath: /xxxx/x 
          }
        }
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants