@Beko Pharm Apparently from nodejs v12 onwards it automatically sets the heap limit dependent on the machine. I guess as a simple user I had sort of assumed everything automagically to be correct, but that's from v12 onwards. The internet says that in browsers you have hardly any control over the max heap setting, while in node.js you can use a command line switch, which is documented as 'not part of the official api so likely to change'. For now it will just be more RAM in the VPS...
I guess I should have known since I did a bit of nodejs development in the past...
Ah, one of those, where increasing the heap only makes the crash occur later. I know these, I've occasionally made these... Also, by increasing the heap beyond available ram, you can make the crash happen really slowly, due to swapping.
Beko Pharm
in reply to Gidi Kroon • • •Gidi Kroon likes this.
Gidi Kroon
in reply to Beko Pharm • •@Beko Pharm Apparently from nodejs v12 onwards it automatically sets the heap limit dependent on the machine. I guess as a simple user I had sort of assumed everything automagically to be correct, but that's from v12 onwards. The internet says that in browsers you have hardly any control over the max heap setting, while in node.js you can use a command line switch, which is documented as 'not part of the official api so likely to change'. For now it will just be more RAM in the VPS...
I guess I should have known since I did a bit of nodejs development in the past...
Gidi Kroon
in reply to Gidi Kroon • •