[Bug]: When using winston v3 on node14.18.3, there seems to be a memory leak event.

🔎 Search Terms

memory leak

The problem

I found memory leaks when using winston v3.7.2.

node test-winston.js 2> /dev/null

RSS: 28.9921875 MB
heap used/total: 4.790740966796875/8.57421875 MB
...
... snip ...
...
RSS: 195.984375 MB
heap used/total: 49.476966857910156/50.82421875 MB

What version of Winston presents the issue?

3.7.2

What version of Node are you using?

v14.18.3

If this worked in a previous version of Winston, which was it?

v2.4.5

Minimum Working Example

const w = require('winston')

setInterval(() => {
    w.error('test'.repeat(100))
}, 10)

setInterval(() => {
    const MB_DIV = 1024 * 1024;
    const usage = process.memoryUsage();
    console.log(`RSS: ${usage.rss / MB_DIV} MB`);
    console.log(`heap used/total: ${usage.heapUsed / MB_DIV }/${usage.heapTotal / MB_DIV} MB`);
}, 1000);

Additional information

In v2.4.5, the increase in memory usage has not occurred as in this case.

[ahmedtalhakhan]

@zizifn We are getting the issue with transport configured as below

transports: [
			new winston.transports.Console()
		],

[wbt]

@wbt I’m using node v13.8.0 and latest version of winston logger. Also, I have opened a separate question regarding the issue we are facing and have added all the details along with how we can reproduce the issue as well: #2233, as we’re able to reproduce the issue pretty much every time, Kindly check this and provide your feedback.

That doesn’t provide “all the details along with how we can reproduce the issue” - it isn’t even logging one message, let alone enough to be overwhelming

Also, it is high priority issue for us as it is effecting our prod environment. If it doesn’t get fixed, we’ll unfortunately have to consider other loggers.

That is not the threat you might think it is. If you need contracted reliability you’ll have to pay a service provider for that.
You can probably pay less for an engineer to start from something that mostly works but has a few bugs (and contribute those working solutions back to the community, where the benefits can be all shared and better maintained) than to start from scratch. If you think another logging library is a better starting point, please feel free to use that. If you’re interested in providing some serious funding to the Winston project, please say so. It currently has none, and businesses relying on it have no right to insist that very-limited-time volunteers burn hours trying to fix issues that you and not we are encountering, especially when provided reports don’t make it easy to reliably reproduce the problem.