@google-cloud/PubSub@1.x has increased memory usage compared to 0.29.1

@pmcnr-hx this memory issue sounds a bit different than what folks were initially seeing in #770 (which was a ceasing up of message processing), so I’ve created this new tracking issue.

Running In Debug Mode

If it’s not too much of a bother, could I get you to run your system with debugging enabled:

process.env.GRPC_TRACE = 'all';
process.env.GRPC_VERBOSITY = 'DEBUG';
const {PubSub} = require('@google-cloud/pubsub');

☝️ I’m curious to see if there is any odd behavior immediately before the message fails to process.

Memory Usage

Do you have any graphs you could share of the memory spiking behavior caused by @grpc/grpc-js, vs., grpc.

Environment details

@pmcnr-hx mind providing this information, with regards to OS/Runtime, are you on Google App Engine, Kubernetes Engine?

• OS/Runtime: ?
• Node.js version: ?
• @google-cloud/pubsub version: 1.1.3

Steps to reproduce

@pmcnr-hx it sounds like the memory issue you run into happens after a few hours of processing, what does the workload look like?, e.g., messages per minute, what type of work happens as the result of a message.

1. ?

see #770

[bcoe]

@Legogris @vigandhi @ibarsi @bsato212 if anyone has the cycles to test the dependency out, could I bother you to try the dependency:

npm i @google-cloud/pubsub@next

☝️ I’ve released version 1.1.6-beta.0 of PubSub, which hopefully addresses some lingering memory issues that folks were seeing.

---

@ibarsi @vigandhi I have not floated a similar patch for @google-cloud/logging-bunyan, if this seems to be where you’re seeing the issue, I can do so, but let’s move the conversation to that repository.

[feywind]

I’m going to go ahead and close this for now since it’s been idle, but please do re-open/comment if needed.