Stuck on an issue?
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.
nodejs-spanner-memory-leak
See original GitHub issue- Is this a client library issue or a product issue? As soon as a (read/write) transaction is initiated, it looks like some memory is leaked, or at least not reclaimed fast enough. Eventually closing the Database releases the memory, but obviously this defeats the purpose of re-using a pool of sessions.
- OS:
- Node.js version: 5.16.3
- npm version:
@google-cloud/spannerversion:
Steps to reproduce
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Client leaks memory - repro provided with single getInstances ...
I have a specific use case where I need to be able to create multiple Spanner clients with different credentials inside a single...
Read more >Isolating and fixing a memory leak in a real Node.js web ...
There are many good articles out there about how to diagnose a memory leak in Node, but most of them focus on over-simplified...
Read more >Getting started with Spanner in Node.js - Google Cloud
Objectives. This tutorial walks you through the following steps using the Spanner client library for Node.js: Create a Spanner instance and database.
Read more >@google-cloud/spanner - npm
Cloud Spanner Client Library for Node.js. Latest version: 6.6.0, last published: 11 days ago. Start using @google-cloud/spanner in your ...
Read more >Google Cloud Spanner: Stream Data from a Query ... - Medium
Each row is written in a separate transaction. NodeJS will apply back-pressure to the read stream and keep the memory consumption low, as...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
That @flovouin So we are able to see a memory leak in readInTransaction @olavloite Will be looking into it
Oops, sorry for the delay, didn’t noticed the ping. We’re still on a 5.x. so I can’t tell yet.