[Bug]: possibile memory leak leads to node process exit in express.js web app #2237
Comments
|
As additional information, the problem was a big stopper for us so we moved to another logging library (pino) and the memory problem disappeared. |
|
I'm sadly experiencing same issue. For me it exits the node process if I try to log an instance of AxiosError. |
Facing same issue too. I move to pino and problem is solved. |
|
Same issue, memory is leaking. Any plans to fix this? |
|
In my case memory was leaking due to improper creation of logger instances. I created a shared logger options object and used it to instantiate multiple loggers in my code: Specifically, it seems like |
|
memory leak originates from one of the dependency package
|
|
Possibly related: BridgeAR/safe-stable-stringify#41 (which also cites a solution of using a maximumDepth option to safe-stable-stringify). |
|
Hello everyone! this.logger = WinstonModule.createLogger({
format: winston.format.uncolorize(),
transports: [
new winston.transports.Console({
format: winston.format.combine(
winston.format.timestamp(),
winston.format.ms(),
utilities.format.nestLike()
),
}),
],
level: "debug",
});Running it locally everything is working fine, and my memory heap is fine: Local env:
When I push it, I use a docker image, and this is what I have It consumes all my heap memory. My container is using In order to get this weird behaviour quickly I wrote this code inside my bootstrap function: setInterval(() => {
console.error('test'.repeat(1000));
}, 10);
setInterval(() => {
const MB_DIV = 1024 * 1024;
const usage = process.memoryUsage();
fs.appendFile(
'message.txt',
`${new Date().toISOString()} heap used/total: ${
usage.heapUsed / MB_DIV
}/${usage.heapTotal / MB_DIV} MB\r\n`,
function (err) {
if (err) throw err;
console.log('Saved!');
},
);
}, 1000);Is there anything I'm missing that can cause this issue? [update] |
🔎 Search Terms
winston memory leak
The problem
After replacing console.log with winston 3.8.2 we are experiencing a sudden exit of the node process with this error:
This is the JS stacktrace:
This is the winston configuration:
What version of Winston presents the issue?
v3.8.2
What version of Node are you using?
v14.20.1
If this worked in a previous version of Winston, which was it?
No response
Minimum Working Example
This is the app.ts
Additional information
No response
The text was updated successfully, but these errors were encountered: