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.
Version 2.6.0 Memory Leak
See original GitHub issueI’ve been using ibm_db for a few years now in a few applications without problems. I had my package.json set to use the latest version of ibm_db, which worked great for me until version 2.6.0. When 2.6.0 released, suddenly my application quickly ran out of memory, every time it rebooted it ran out of memory again. I spent 2 days reverting code and analyzing my own memory usage, until I realized it wasn’t caused by something my team had done, but rather something in this new build of ibm_db. As soon as I reverted my package.json file back to version 2.5.3 the memory leak went away.
I use the query function with connection pools.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:9 (4 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’m using v2.6.1 with node v10 and we are most definitely experiencing a memory leak. Our app is constantly having to restart in order to be able to query via ibm_db driver.
We’re still using Node v10. Is v11 or v12 recommended for ibm_db@2.6.0/2.6.1 given these changes?