This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-26
Channels
- # aleph (3)
- # beginners (98)
- # boot (24)
- # cljs-dev (13)
- # cljsrn (16)
- # clojure (97)
- # clojure-dusseldorf (2)
- # clojure-italy (2)
- # clojure-losangeles (2)
- # clojure-russia (48)
- # clojure-spec (28)
- # clojure-uk (79)
- # clojurescript (79)
- # community-development (2)
- # cursive (4)
- # datomic (35)
- # duct (1)
- # events (1)
- # fulcro (43)
- # heroku (1)
- # jobs (1)
- # lein-figwheel (2)
- # luminus (1)
- # lumo (12)
- # nyc (1)
- # off-topic (6)
- # om (1)
- # pedestal (7)
- # portkey (9)
- # proton (1)
- # re-frame (45)
- # reagent (27)
- # rum (2)
- # shadow-cljs (78)
- # spacemacs (3)
- # specter (2)
- # testing (2)
- # vim (41)
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.
@hlolli still looking for feedback https://github.com/anmonteiro/lumo/issues/218
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...
not possible
it’s gotta be compile time in Lumo
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.
@hlolli what I’m suggesting in the issue is Lumo should ship with sensible defaults
we shouldn’t require you to compile Lumo
ok, I hope there'll be feedback, I'd assume 512mb should be plenty, what's the current value?
the current value is 1.5GB