Let's see if we can wrap up the #WriteFreely v0.10 release today.
@writeas_dev is it possible to limit RAM usage or force GC to work on smaller values? I'm running the latest version of WriteFreely, private instance for myself only. After some time it takes all available memory causing some apps to break (f.ex. some python scripts raise "cannot map shared object" exception).
2 screenshots. 1st: state when WF takes all available RAM, 2nd: directly after restart via Systemd.
@writeas_dev correction: errors which I see in Python objects when free RAM is almost empty are:
RuntimeError: can't start new thread
and
vedis.cpython-35m-x86_64-linux-gnu.so: failed to map segment from shared object
(I'm using Vedis library)
This doesn't directly relate to WriteFreely, but I think these are symptoms of lack of Free RAM which is caused (probably) by WF
@Groosha Hmm, at first that sounds like there might be a memory leak, but am I right in saying that you have 9 instances of WF running at once? I think that's what's causing it.
(For comparison, Write.as is serving 60k+ users and using only 26MB of RAM after several days.)
Either way, if you could create an issue on GitHub we can look into it.
@writeas_dev nope, only one (1) instance of WriteFreely. Most likely htop shows all threads, not only processes.
Anyway, I've opened an issue on Github: https://github.com/writeas/writefreely/issues/133
Thank you for your time!
v0.10, coming up...