Pubsub emulator memory leak >= @google-cloud/pubsub 3.0.0 about google-pubsub-emulator HOT 3 CLOSED

My experience is to use 1 instance of google-cloud/pubsub per google project.
Technically the memory leak is in the google-cloud/pubsub package.
I haven't used this package for a while because I also use docker image setup and the container starts very slowly. So I use docker compose to start the container, delete and create the topics and subscriptions in the before/beforeEach section.

I decreased our test time drastically with this setup even if the test run serial instead of parallel.

I think I could optimise this library to use 1 google-cloud/pubsub instance per project, but I don't know your full setup so maybe it would not help you at the end of the day.

from google-pubsub-emulator.

@ert78gb Hey! Sorry - I closed this issue without seeing your comment. It did turn out to be a google-cloud/pubsub issue that didn't like versions >= 3.0.0 and <= 3.3.0. Once we upgraded to 3.5.0, the memory leak was resolved!

from google-pubsub-emulator.

Thx for the update

from google-pubsub-emulator.