We’re aware of the memory issue and are working on...
# general
j
We’re aware of the memory issue and are working on a refactor right now which will take care of it. I think this issue is not in 0.8.5 so that may be a better option but I’m also thinking there’s some simple docker stuff we can do to restart the container once it hits X memory. The container starts really fast so shouldn’t cause any noticeable issues and will be a lot quicker of a fix