RangeError: Maximum call stack size exceeded

[kaue]

Node: v6.3.0
winston: ^2.2.0
winston-mongodb: ^1.6.0

Stack:
RangeError: Maximum call stack size exceeded at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:79:26) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52) at Object.exports.clone (/workspace/node_modules/winston/lib/winston/common.js:110:52)

[shahimclt]

I had encountered this error in my project. It turned out passing some specific kinds of objects causes winston to print very huge logs causing some kind of overflow. In my case it was caused by printing mongodb query results.
See this SO question and check if your issue is similar.

P.S: Any contributors viewing this, please check out that SO question (I am the OP) and try to provide any input if you can.

[kaue]

I think this time the problem is that i was printing a function as metadata.

[thinkkevin]

check #862

[mdnorman]

I have also run into this problem when logging the error object coming from the soap library. This is because the error contains the original request object, and request objects for some reason have circular references. I only see it with the logstash output because it uses the clone function to copy the metadata value into the logstash @fields.

Example line of code:
logger.error('Some error info:', err)

[mdnorman]

Updated #474

[shahimclt]

Any Updates?

I have been constantly checking #862, #474 and #914 for an update. I also have a question posted here which too hasn't gotten any response.

[jifeon]

The fix in #977

[vbardales]

👍

[fega]

I'm still getting the same problem when a custom formater is used