Insane memory usage and stalled jobs on development with tsc --watch

[emintatli]

Version

v5.26.2

Platform

NodeJS

What happened?

running with tsc --watch or nodemon casuses insane amount of ram usage and/or stalled jobs.
Details:
https://stackoverflow.com/questions/79197308/insane-amount-of-ram-usage-with-bullmq-fetch?noredirect=1#comment139654212_79197308

How to reproduce.

https://github.com/emintatli/bullmq-issue

Described in the repo

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[manast]

Since you mention that it works well without tsc --watch or nodemon, then the watch mechanism of these tools may be messing up the app. It is a bit difficult to understand from your description if the problem is in Redis memory consumption or in the application itself. In any case, I think this issue is a bit out of the scope of BullMQ as it seems to be something quite specific to these tools, I think you did right in asking in stack-overflow as there may be more expertise in this area there than here.