Closed cooljeanius closed 1 year ago
You are going to need to allow Node to use more memory. I will warn that this may cause strange behavior from your device, but it usually does work. I have a package.json
command for this. But that also dumps the build record to a file for debug purposes. The important part is NODE_OPTIONS=--max-old-space-size=12288
which raises the amount of memory Node can claim on my system to 12,288 MB. It appears to only works with multiples of 1024 (1 Gig) and, at least on Linux systems, you cannot make it larger than your on-board RAM, even if you have plenty of Swap space.
You are going to need to allow Node to use more memory. I will warn that this may cause strange behavior from your device, but it usually does work. I have a
package.json
command for this. But that also dumps the build record to a file for debug purposes. The important part isNODE_OPTIONS=--max-old-space-size=12288
which raises the amount of memory Node can claim on my system to 12,288 MB. It appears to only works with multiples of 1024 (1 Gig) and, at least on Linux systems, you cannot make it larger than your on-board RAM, even if you have plenty of Swap space.
ok yeah that seems to have worked
(unfortunately cooljeanius/my_tweetback_archive#1 still seems to be an issue, though...)
update: had to raise the amount from 12288 to 24576 on my latest run...
just putting backtrace here for now; will figure out later: