Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Potential memory leak in Pool
See original GitHub issueHi,
I have a use case where I run quite a lot of batched queries against Postgres (thousands). I recently ran into memory issues on my worker machine and could trace the issue to an apparent memory leak somewhere in the connection pool.
So far it’s just an observation, I didn’t build a proper test case yet. But the memory issue went away when I switched from using a connection pool to single-use connections.
Did anyone notice this too? Seems like a recent issue IMO.
I’m using "pg": "^8.7.3" and "pg-native": "^3.0.1"
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I need self-contained script/file with reproduction case to investigate this. Otherwise there are too many factors involved to pin any memory leak down on pg itself.
Switched to latest version ^8.8.0 & had a try, there’s not much memory taken by “PendingItems”, but still lots of objects produced (the chrome inspector shows the total objects from 700+ raised up to 500K+)