Fix memory leak in process.namespaces

[tlhunter]

Numeric namespace identifiers are never removed from the global process.namespaces object:

cls-hooked/context.js

Line 440 in 066c6c4

process.namespaces[name] = null;

cls-hooked/context-legacy.js

Line 364 in 066c6c4

process.namespaces[name] = null;

[tlhunter]

^ I believe the test runner is having issues. The same failures occur locally in master, as well as other recent open PRs.

[MichaelRBond]

This branch significantly reduces the memory creep I've been seeing with cls-hooked.

[kibertoad]

@Jeff-Lewis Any chance this could be looked at? Btw, if you don't have time for the project anymore (which may be the case judging by amount of commits lately), I would be more than happy to volunteer to help maintain the project.

[kibertoad]

Any updates?..

[Themandunord]

@Jeff-Lewis Any chance to take a look at this?

In production :

[alexgarbarev]

It looks like problem with leak is not in "process.namespaces" but in async_hook leaking. See #60 for details.

[orloffv]

@Jeff-Lewis ping(

[ridakk]

ayn update on this ? 👀

[kibertoad]

@ridakk It seems to be pretty abandoned. Either way, if you are on modern enough Node, migrating to AsyncLocalStorage is preferable.
In case you want to ease up migration from cls-hooked, you could use a compatibility bridge: https://github.com/kibertoad/asynchronous-local-storage

[ridakk]

@ridakk It seems to be pretty abandoned. Either way, if you are on modern enough Node, migrating to AsyncLocalStorage is preferable.
In case you want to ease up migration from cls-hooked, you could use a compatibility bridge: https://github.com/kibertoad/asynchronous-local-storage

@kibertoad thx for the heads up, and yes we are on latest lts but our problem is Sequelize and it still depends on cls-hooked 😩