-
Notifications
You must be signed in to change notification settings - Fork 7.3k
RangeError: Invalid string length --- it should be saying Out Of Memory #14170
Comments
That's an issue from v8 (the javascript engine) not node. ( |
It would help to know how Otherwise, operating on a string that is too large should throw the "Invalid string length" error, so I don't see anything that would be unexpected. As @Fishrock123 mentioned, these errors are thrown from V8, so if you still think that these error messages are not correct, I encourage you to file an issue in V8's issues tracker. Closing for now, but please let us know if you have any question. |
While I do get it this is the wrong place to ask about this issue, this is also the first hit on google, so... Any links to where we could look for a solution to the actual problem? I still think I need to stringify a huge object (to enable people to save and share their Mariox's advancements), certainly over 5mb ( I'll lz compress it later, if this matters to you ;P ). |
I have a problem about this,please help me! |
me too ! 👎 (ubuntu 14.04, nodejs 5.10.1) |
Have to this problem now with json files) try use on ubuntu: cat file1.json file2.json > res.json |
same here, csv-stringify library but this is the first google hit; I'm csv-ing a record from a very very wide table in SQL |
same issue at node v6.2.2 on CentOS 7 |
Same here 7.9.0 - Webpack cannot build |
Same issue here. Ubuntu 16.04, Node v8.1.4 |
is there any fix ? |
same issue… |
facing same issue |
This repo is an archive, if you're still seeing this please open an issue at nodejs/node (if there isn't one there already). |
Please update ERROR message when attempting to call
Today when it runs out of RAM above gives this message
RangeError: Invalid string length
when it clearly should indicate the system is out of RAM.
Searching this error message I see nodejs does recognize
an Out Of Memory condition yet it continues to give a less helpful error message
https://github.com/joyent/node/search?utf8=%E2%9C%93&q=RangeError%3A+Invalid+string+length
The text was updated successfully, but these errors were encountered: