This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-25
Channels
- # aleph (15)
- # beginners (65)
- # boot (46)
- # chestnut (3)
- # cider (1)
- # clara (11)
- # cljs-dev (5)
- # cljsjs (4)
- # cljsrn (13)
- # clojure (180)
- # clojure-dev (2)
- # clojure-italy (10)
- # clojure-russia (62)
- # clojure-spec (6)
- # clojure-uk (85)
- # clojurescript (45)
- # community-development (11)
- # crypto (3)
- # cursive (10)
- # datomic (94)
- # defnpodcast (2)
- # fulcro (4)
- # heroku (1)
- # hoplon (4)
- # jobs (3)
- # juxt (10)
- # leiningen (1)
- # luminus (4)
- # mount (13)
- # music (1)
- # off-topic (10)
- # onyx (2)
- # portkey (15)
- # proton (2)
- # re-frame (16)
- # reagent (10)
- # shadow-cljs (194)
- # spacemacs (2)
- # specter (2)
I'm using aleph and manifold for communicating with the StarCraft II AI API. Yesterday I tried my hand at a run-loop and I completed one of the challenges using Clojure (yay!). I'm using alephs websocket to connect to the api which uses protobuf to communicate. And I utilize streams for the run-loop, but after around 100 steps into the game I get a memory leak notification which later makes the websockets requests fail.
Sep 25, 2017 12:26:19 PM io.netty.util.ResourceLeakDetector reportTracedLeak
SEVERE: LEAK: ByteBuf.release() was not called before it's garbage-collected. See for more information.
I'm not sure what could be causing it. I found https://groups.google.com/forum/#!msg/aleph-lib/-41TvS0uKVM/KF7PE_iOErwJ but that should now not happen with the defaults anymore.
Not sure if the stacktrace is visible on slack, I don't have any storage space in my slack workspace
Quickly browsing the code, I'm not sure what is supposed to release the bytebufs allocated by client.clj:420
it might help to see what I am doing, might be doing stupid stuff: https://github.com/bbss/cljsc2/blob/master/src/cljsc2/clj/core.clj#L56 create a websocket connection to the starcraft 2 client https://github.com/bbss/cljsc2/blob/master/src/cljsc2/clj/core.clj#L33 put requests on the websocket connection
that does sound very promising, I should have checked that out myself. Fingers crossed haha.