Clojurians
#lumo
<
2017-09-26
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

hlolli22:09:50

Is there a way to increase the memory, I'm running audio engine within lumo and I know that I'm calling buffer heavy process, what I get is

lumo: malloc.c:2369: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.

hlolli22:09:36

hm ok, so this is a compile time setting?

hlolli22:09:57

found the answer, and its a startup option node script.js --max-old-space-size=8192 and there are plenty of node flags of course. We could add a lumo flag that takes a vector of native node flags lumo --node-flags ["--max-old-space-size=8192"] etc...

anmonteiro22:09:24

not possible

anmonteiro22:09:38

it’s gotta be compile time in Lumo

hlolli22:09:10

ok, for my part I'm ok with compileing lumo for my usecase. Guess this could be documented then. I guess these are relatively rare edge cases.

anmonteiro22:09:40

@hlolli what I’m suggesting in the issue is Lumo should ship with sensible defaults

anmonteiro22:09:45

we shouldn’t require you to compile Lumo

hlolli22:09:18

ok, I hope there'll be feedback, I'd assume 512mb should be plenty, what's the current value?

anmonteiro22:09:36

the current value is 1.5GB

hlolli23:09:14

I misread that 1.5GB was the maximum settable limit and 512MB was default. I compile lumo with 8gb limit by setting v8.setFlagsFromString('--max_old_space_size=8192'); in cli.js