| 29 Dec 2023 |
 hexa | wir sind viele 😛 | 19:52:21 |
 Wanja Hentze | dismantling the anglosphere one question at a time | 19:52:24 |
 @joepie91:pixie.town | In reply to @hexa:lossy.network
joepie91 🏳️🌈: I don't understand how it failed to acquire more memory tbh right, so I expect that it's hitting the heap size limit | 19:52:40 |
| @joepie91:pixie.town | the various space_size flags for v8 control this | 19:52:59 |
| hexa | for which it determined the size by itself? | 19:53:03 |
| @joepie91:pixie.town | there's something like node --v8-flags that should show you the relevant flags in your Node/V8 version | 19:53:17 |
| @joepie91:pixie.town | (not sure if that's exactly the right parameter) | 19:53:29 |
| hexa | ok | 19:53:39 |
| @joepie91:pixie.town | In reply to @hexa:lossy.network
for which it determined the size by itself? it's set to some default, I don't remember how much, couple gigs | 19:53:47 |
| @joepie91:pixie.town | ah it seems that newer Node/V8 versions just have a --max-heap-size flag | 19:54:35 |
| @joepie91:pixie.town | so try --max-heap-size 8G or so and see if that works :p | 19:54:50 |
| hexa | --max-heap-size (max size of the heap (in Mbytes) both max_semi_space_size and max_old_space_size take precedence. All three flags cannot be specified at the same time.)
type: size_t default: --max-heap-size=0
--initial-heap-size (initial size of the heap (in Mbytes))
type: size_t default: --initial-heap-size=0
| 19:55:09 |
| @joepie91:pixie.town | right so I guess 8096 is the right value then | 19:55:41 |
| hexa | 0 sounds like autopilot or inf | 19:55:43 |
| @joepie91:pixie.town | for the max | 19:55:47 |
| @joepie91:pixie.town | hm | 19:55:55 |
